🚀 go-pugleaf

Ryan Mills schrieb:

> I'm having a helluva time trying to get dcc32 to compile a runtime package.
> 
> I'm using D7 (ent) version of dcc32 and the runtime package I'm trying to 
> compile builds just fine in the IDE.  But when I try to use dcc32 I get the
> error message "unable to locate the package RTL".
> 
> Now I know that the d7 package source reads RTL, instead of RTL70, and 
> that ide massages that to be RTL70 when it's doing the compile but how do I 
> get dcc32 to do the same?  With out modifying the dpk file prior to using 
> dcc32!!

Here is how my (private) tool builds the command line for a .dpr file:

"%3:s\dcc32.exe" -Q -B -W -H -E"%7:s" -U"%4:s;%5:s" -R"%5:s" "%1:s%2:s"

and for a .dpk file:

"%3:s\dcc32.exe" -Q -B -W -H -N"%5:s" -LE"%6:s" -LN"%5:s" -U"%4:s;%5:s" -R"%5:s" "%1:s%2:s"

The meaning of N in the %N:s numbers above is

{
0: Current directory name
1: File name to compile without directory or extension
2: File extension incl dot
3: Build tools directory
4: Borland library directory (.dcu, .dcp, .dfm, and .res files)
5: Unit destination directory (target for package .dcu, .dcp and .res
files)
6: Package destination directory (target for .bpl files)
7: Binary destination directory (target for .exe and .dll files)
8: Windows command processor (cmd.exe incl. path)
}

(There are some more lookups in this list since it's used to build other
command lines, too.)

-Michael