[DUG] Command Line Compiler
Conor Boyd
Conor.Boyd at trimble.co.nz
Mon Nov 2 13:35:22 NZDT 2009
That's a good point Jolyon.
Our build script temporarily renames the [project name].cfg to something
completely different to ensure it doesn't clash with the dcc32.cfg the
build script writes.
C.
-----Original Message-----
From: delphi-bounces at delphi.org.nz [mailto:delphi-bounces at delphi.org.nz]
On Behalf Of Jolyon Smith
Are you sure you do not have a DCC32.CFG that the compiler is picking up
and using in preference to your project CFG files? There doesn't appear
to be any way to prevent that from happening, other than making sure you
don't have a DCC32.cfg file "polluting" your build environment (where
you aren't using one - if you are using one then you presumably do so
precisely to AVOID having project specific CFG files, but having *both*
wouldn't appear to be an option).
-----Original Message-----
From: delphi-bounces at delphi.org.nz [mailto:delphi-bounces at delphi.org.nz]
On Behalf Of John Bird
Like many I have need to recompile a whole suite of programs, and the
command line compiler seems ideal for this.
However it seems to put the exe files in the same folder as the project
files, which means that it is not following the project setups eg for
Directories/Conditionals Output folder.
I tried comapring the exe files made by the IDE and the command line, eg
for
one they are the same size but do have some binary differences.
What are these other differences?
Ideally I want to set up the command line compiler to produce the same
as my
IDE compiler, but this does not seem obvious. Or turn on or off some
well defined things, such as turn on optimisations
I found a good article such as
http://www.delphi3000.com/articles/article_4585.asp?SK=
But I hesitate to use the command line if there are other unknown
differences in the exe produced.
But I am getting mightily bored with opening one project after another
and hitting F9
More information about the Delphi
mailing list