🚀 go-pugleaf

In developing my smokebuilder application for automating the use of 
DCC32, I found the same thing:  that the options set in the .dpk file 
always take precedence.  So, as with the .cfg file, I found I needed to 
replace it as part of the process.

Brandon Smith
http://synature.com/synature/delphi/index.htm


Jens Berke <noreply@jensberke.de> wrote in news:412db030$1
@newsgroups.borland.com:

> I'm just digging into these questions  as well. My tests so far showed
> that the options stored in the DPK-file itself are _always_ used, no 
> matter what's in the CFG-file, the DCC32.CFG file or in the command 
line 
> parameters you pass to DCC32.
> With _one_ exception: if you have a $DEFINE in the DPK-file and provide 
> a -DMyDefine in the commandline, the $DEFINE of the DPK file is 
> _ignored_ and the one of the commandline is used.
> 
> If someone can confirm this behaviour I'd be glad
> 
> Jens
> 
>