> ----- Original Message -----
> From: mikcaau
>
> > > From: pietro
> > >
> > > I would like to know how and were to implement different setup for the
> > > compiler and other stuff, to add/remove debug infos etc to the final
> > > .exe
> > >
> > > ----- Original Message -----
> > > From: Jeremy Grand
> > >
> > > Pietro, take a look at Project/Options/Compiler.
> >
> > don't forget to run build on the entire project with every changes to
> > compiler-options.
> >
> > while we are on the subject,
> > I really admire the simplicity of C language's makefile,
> > in such that we can build debug and release executable in a single
> > compile.
> > I wonder if it is available on Delphi-X ( I forgot the name ;) ) ?
>
> Since all settings can be adjusted using inline compiler directives it
> is quite simple to set a user diective to set the compiler to the
> state that you want. This is normally done using an include file used
> in every unit
>
> example
> {Define DebugBuild)
>
> {IfDef DebugBuild}
> //set debug switches
>
> {$Else}
> //unset debug switches
>
> {$EndIf}
>
> Mick
Is that in {$I ...} or in *uses* clause?
Delphi doesn't check if any include file --$I-- has recently been edited,
so if there is one in a unit, that unit's dcu-file will not be updated
in a normal compile.
This is off-topic, but I'd tried to use {$Define DEBUG} in include
file for a simple debug checking process, in place of *assert*, and
most of the time I forgot to run a complete build.
The resulting dcu's got mixed up and behaves unexpectedly.
( bummer )
I found that it is a lot easier??? to put {$Define DEBUG}
on *every* units, eeuw...
( and one more for {$Define TEST}, that's two )
------------
FIreHAzaR:-D
West Java, Indonesia
