Command Line Compiler

Gordon Turner

unread,

May 16, 2008, 5:19:49 PM5/16/08

to

I'm just now experimenting with the command line compiler (to use with
an automated build tool). It seems like the compiler does not know
about the Library Paths that load with Delphi (I'm using D7 right now)
and the Help file is less than helpful in figuring out how to compile my
program.

Are there any other resources on how to setup and configure DCC32.exe?
Also, how to pass conditional variables, additional search paths, etc.

Gordon Turner

Remy Lebeau (TeamB)

unread,

May 16, 2008, 5:31:59 PM5/16/08

to

"Gordon Turner" <D...@nospam.com> wrote in message
news:482d...@newsgroups.borland.com...

> It seems like the compiler does not know about the Library Paths
> that load with Delphi (I'm using D7 right now)

Because they don't exist. You have to specify the paths on the command line
via the -I, -R, and -U parameters.

> Are there any other resources on how to setup and configure DCC32.exe?

Have you tried simply running it without any parameters specified? It will
tell you what parameters are available for you to use.

> Also, how to pass conditional variables

The -D parameter.

> additional search paths, etc.

See above.

Gambit

Jim

unread,

May 16, 2008, 9:02:22 PM5/16/08

to

> > Are there any other resources on how to setup and configure
> > DCC32.exe?

There are a couple missing from the list and are important:

-LE"d:\borland\delphi7\Projects\Bpl"
-LN"d:\borland\delphi7\Projects\Bpl"

I believe the first one is for the package *.bpl files and the other is
for the *.dcp files. Here they point to my default folder for compiled
package files.

Jim
--
www.mustangpeak.net

Chris Burrows

unread,

May 16, 2008, 11:33:12 PM5/16/08

to

Gordon Turner <D...@nospam.com> wrote:
>I'm just now experimenting with the command line compiler (to use with
>an automated build tool). It seems like the compiler does not know
>about the Library Paths that load with Delphi (I'm using D7 right now)

If:

a) it is not too late / infeasible to choose another tool

b) your time costs money

consider using an automated build tool that 'knows' about all of the Delphi settings and options and presents them in a familiar way. I (strictly as a very satisfied customer) highly recommend VSoft's FinalBuilder:

http://www.finalbuilder.com/

--
Chris Burrows
CFB Software
http://www.cfbsoftware.com/cp

Dennis Passmore

unread,

May 17, 2008, 4:28:47 PM5/17/08

to

What I have seen quite often in the past is that some programmers
do not always check in changes to the project.cfg file when they
change a project and DCC32.EXE reads the project.cfg file after
parsing DCC.CFG first to find out where things are located. You
can always create a custom something.cfg file and pass a command
line param to DCC32.exe to read it instead with your build tool.

Rudy Velthuis [TeamB]

unread,

May 18, 2008, 11:01:39 AM5/18/08

to

Gordon Turner wrote:

Try to look for YourProjectName.cfg and for dcc32.cfg. The latter is
IIRC the name for the default settings, while YourProjectName.cfg
contains settings for YourProjectName.dpr. These .cfg files are
generated by the IDE, AFAIK.

DCC32, when run without any parameters, will display a long help text
giving the meanings of its command line parameters.
--
Rudy Velthuis [TeamB] http://www.teamb.com

"Never mistake motion for action."
-- Ernest Hemingway (1899-1961)