🚀 go-pugleaf

Jesper Hogstrom (Borland) wrote:
> Mitch wrote:
> 
>> I've been struggling to ues DCC32 and the project CFG file to automate 
>> the build of a large project containing several executables and 100's 
>> of units. After struggling to get the paths set I found that it wasn't 
>> correctly evaluating some IFDEF's in my code. Despite the fact that a 
>> directive was not defined it would treat it as defined. I finally 
>> worked  around the problem by adding an UNDEF in each unit that 
>> evaluated it.
>>
>> {$IFDEF REPORTWORKS}
>>   {$UNDEF ROCKWORKS}
>>   {$ENDIF}
>>
>> This doesn't seem the right way to do this and I'm sure I must be 
>> missing something.
> 
> 
> How does your various config files look? What if you compile with 
> --no-config, are the defines still set?
> 
> --Jesper

I don't think it would compile at all without the config. The config is 
fairly large with all the paths to units and libraries that I needed. I 
need to go back and remove some extra path stuff that really isn't 
needed. I used the IDE generated CFG as the starting point and added 
path stuff until it would compile. I could post it if you really want to 
take a look. I should have mentioned that I'm using D7 Pro.

Mitch
Mitch