Setting up a development environment for hacking GDC
Iain Buclaw via D.gnu
d.gnu at puremagic.com
Thu Oct 16 09:44:59 PDT 2014
On 16 October 2014 12:51, Mike via D.gnu <d.gnu at puremagic.com> wrote:
> On Sunday, 12 October 2014 at 09:11:16 UTC, Iain Buclaw via D.gnu wrote:
>
>>
>> Incremental Builds:
>>
>> When you make a change to either the gdc or gcc sources, running make
>> inside objdir will keep on doing incremental builds for you. Some
>> exceptions to the rule:
>>
>> * Adding/Removing files from libphobos or libdruntime require you to
>> re-run the setup-gcc.sh script
>>
>> ./setup-gcc.sh --update ../gcc-devel
>>
>> * I have noted in certain circumstances (updating the frontend
>> mostly), changes to dfrontend/idgen.c or dfrontend/impcnvgen.c
>> sometimes do not trigger rebuilds of other sources. When this occurs,
>> crashes or errors will look rather confusing. That's because the
>> symbol table between two object files differ. Clean out all objects
>> from the gdc build directory and re-make it.
>
>
> I see the instructions below for cleaning GDC and libphobos/libdruntime, but
> to clean GCC also, can we just do `make clean`?
>
'make clean' clears everything so you'll start from zero again.
Alternative clean routines you can do via the Makefile:
Only D:
make -C gcc d.mostlyclean
All front-ends (C, C++, ...):
make -C gcc lang.mostlyclean
All GCC front-ends and backend (but not dependencies):
make -C gcc clean
Regards
Iain
More information about the D.gnu
mailing list