🚀 go-pugleaf

Couple of hints from what I learned in making my utility, which is at
http://synature.com/delphi

1.  Don't count on dcc32.cfg being used by the command line compiler.  It 
will use project.cfg if it exists.  Therefore you need to replace your 
project.cfg with one that contains the options you want when you fire the 
command line compiler.  In my experience, even if project.cfg doesn't 
exist, the command line compiler simply takes the defaults, doesn't 
always seem to find dcc32.cfg even if it does exist.

2.  Always enclose the paths with double quotes and be sure to put a 
semicolon between each one. The double quotes must be there if there are 
any spaces in the path. Be sure to end the line with ;"
Like this (note this is one line, wrapped by my newsreader):

-U"i:\d5\Delphi5\LIB;i:\d5\Delphi5\BIN;i:\d5\Delphi5\IMPORTS;i:\d5
\Delphi5\PROJECTS\BPL;i:\d5\Delphi5\DCU;i:\d5\Delphi5\SOURCE\TOOLSAPI;L:
\CURWORK\DELPHI\NTIER\CLIENT;L:\CURWORK\DELPHI\NTIER\COMPONENTS;L:
\CURWORK\DELPHI\NTIER\COMPONENTS\TLOGON\SERVER;L:\CURWORK\DELPHI\NTIER
\COMPONENTS\TLOGON\CLIENT;L:\CURWORK\DELPHI\NTIER\COMPONENTS\TLOGON;L:
\CURWORK\DELPHI\NTIER\PIETTE\ICS\DELPHI\VC32;L:\CURWORK\DELPHI\NTIER
\PIETTE\MIDWARE\DELPHI\VC32;L:\CURWORK\DELPHI\NTIER\APPSERVER
\SERVEROBJECTS;L:\CURWORK\DELPHI\NTIER\APPSERVER;"

It will read up to 1024 characters, but you need to back up and be sure 
it ends with ;", don't try to break a path in the middle.

If it is longer than 1024, like Mike said, just add another -U"path.." 
line with the rest of the paths.  I had a job that took four -U lines.  I 
usually simply copied the entire set of -U lines and put -I, -R and -0 in 
front if I had any includes, resources or objects, just to safe.

3.  In Windows NT and W2K and XP, theoretically the maximum length of a 
single path is quite long, and the directory system will let you make 
them very long.  In practice, however, when using the command line 
compiler, it turns out to be closer to 163.  If you are placing the 
compiled exe in a different directory, using the -E option, I found that 
the limit was much less and had to use ExtractShortPathName for the 
destination.

Have fun

Brandon Smith


"Mike Williams [TeamB]" <mlwilliams@gmail.com> wrote in
news:Xns9575781D6A7Amikewteamb@207.105.83.66: 

> On 01 Oct 2004, "Michael Rabatscher" <rabatscher@tom-signal.com>
> wrote: 
> 
>> Is there a limitation in the length of searchpaths in dc32.cfg (ours
>> is about 1050 characters long due to very
>> much 3rd party code) or what can that be?
> 
> Yes, there's a limitation on the path length (I don't recall what it
> is). 
> 
> You can avoid this by breaking it up onto multiple lines - which makes
> it more readable anyhow:
> 
> /uc:\Program Files\Path1
> /uc:\Program Files\Path2
> /uc:\Program Files\Path3
> /uc:\Program Files\Path4
>