• Andrei Alexandrescu (5/5) Jun 29 2020 Is there a way to see what build.d is doing from the invocation of make?...
• Sebastian Wilzbach (6/13) Jun 29 2020 Solution: stop using the legacy Makefile wrapper which was only left in
• Andrei Alexandrescu (2/8) Jun 29 2020 How would that work with AUTO_BOOSTRAP?
• Sebastian Wilzbach (9/18) Jun 29 2020 Auto bootstrapping just downloads a (somewhat arbitrary) dmd version to
• Andrei Alexandrescu (2/24) Jun 29 2020 Cool, thanks!
• MoonlightSentinel (3/8) Jun 29 2020 make -f ***.mak VERBOSE=1 ....

Andrei Alexandrescu <SeeWebsiteForEmail erdani.com> writes:

Is there a way to see what build.d is doing from the invocation of make? 
The only way I found was to do surgery on src/posix.mak and add 
--verbose to:

	$(RUN_BUILD) $ 

Thanks!

Sebastian Wilzbach <seb wilzba.ch> writes:

Solution: stop using the legacy Makefile wrapper which was only left in
the source repository to ease the transition for dmd packagers and CI
systems.
tl;dr:

./src/build.d -v

On 29/06/2020 19.51, Andrei Alexandrescu via Dlang-internal wrote:
 Is there a way to see what build.d is doing from the invocation of make?
 The only way I found was to do surgery on src/posix.mak and add
 --verbose to:
 
     $(RUN_BUILD) $ 
 
 Thanks!

Andrei Alexandrescu <SeeWebsiteForEmail erdani.com> writes:

On 6/29/20 1:57 PM, Sebastian Wilzbach wrote:
 Solution: stop using the legacy Makefile wrapper which was only left in
 the source repository to ease the transition for dmd packagers and CI
 systems.
 tl;dr:
 
 ./src/build.d -v

How would that work with AUTO_BOOSTRAP?

Sebastian Wilzbach <seb wilzba.ch> writes:

On 29/06/2020 20.30, Andrei Alexandrescu via Dlang-internal wrote:
 On 6/29/20 1:57 PM, Sebastian Wilzbach wrote:
 Solution: stop using the legacy Makefile wrapper which was only left in
 the source repository to ease the transition for dmd packagers and CI
 systems.
 tl;dr:

 ./src/build.d -v

 
 How would that work with AUTO_BOOSTRAP?

Auto bootstrapping just downloads a (somewhat arbitrary) dmd version to
make setup a little easier/predictable, but you should have a dmd
compiler installed on your system, if not:

. $(~/dlang/install.sh --activate dmd)
./src/build.d -v

If your question is about ensuring that DMD is built with the currently
selected version for bootstrapping, you can still do:

./src/build.d -v AUTO_BOOTSTRAP=1

Andrei Alexandrescu <SeeWebsiteForEmail erdani.com> writes:

On 6/29/20 2:48 PM, Sebastian Wilzbach wrote:
 On 29/06/2020 20.30, Andrei Alexandrescu via Dlang-internal wrote:
 On 6/29/20 1:57 PM, Sebastian Wilzbach wrote:
 Solution: stop using the legacy Makefile wrapper which was only left in
 the source repository to ease the transition for dmd packagers and CI
 systems.
 tl;dr:

 ./src/build.d -v

 How would that work with AUTO_BOOSTRAP?

 
 Auto bootstrapping just downloads a (somewhat arbitrary) dmd version to
 make setup a little easier/predictable, but you should have a dmd
 compiler installed on your system, if not:
 
 . $(~/dlang/install.sh --activate dmd)
 ./src/build.d -v
 
 If your question is about ensuring that DMD is built with the currently
 selected version for bootstrapping, you can still do:
 
 ./src/build.d -v AUTO_BOOTSTRAP=1

Cool, thanks!

MoonlightSentinel <moonlightsentinel disroot.org> writes:

On Monday, 29 June 2020 at 17:51:12 UTC, Andrei Alexandrescu 
wrote:
 Is there a way to see what build.d is doing from the invocation 
 of make? The only way I found was to do surgery on 
 src/posix.mak and add --verbose to:

 	$(RUN_BUILD) $ 

 Thanks!

make -f ***.mak VERBOSE=1 ....