🚀 go-pugleaf

Why do you have \debug on your path if you are compiling a release 
version?  But anyway, a technique that will work is to set up a release 
build in the IDE, making sure everything is correctly checked.  The path 
for a release build should have ..lib first in the path, that's where the 
basic Delphi stuff is,in dcu form such as system.dcu, which is what you 
want.  There is no reason to compile the source of the basic Delphi 
library files.  (This assumes you have been putting your own generated 
DCU somewhere other than the delphi lib directory. And that you haven't 
done a build with any of the \debug source directories on the path.)

Once you can build a release version from the IDE, look at myproject.cfg 
and make sure it has what you want in it.  Then copy it to a file called, 
for example, release.cfg.  When you ready to do a release build with the 
DCC, get into a command window and navigate to the directory where your 
.dpr is.  Replace the existing project.cfg with your release.cfg (i.e. 
copy or rename the IDE generated cfg and rename release to 
myproject.cfg).

You can take a look at my site where I've got notes and a help file 
related to the ins and outs of using the DCC32, albeit with versions 5 
and 6.

http://synature.com/synature/delphi/index.htm

Brandon

ps  I didn't go through your path in detail, but just scanning over it, I 
see that you are going to be including a lot of source files that you 
probably don't want.  Unless you are actually doing changes in the 
supplied components, the only time to include the delphi source is when 
you are tracing down into code to find out something.  For a release 
build, the only source I would include in my path would be the source 
I've written or modified.  Also I would be sure to do a build (-B) and 
not a make, since I wouldn't want one of my old DCU to throw a monkey 
wrench into things.



"Alan Garny" <someone@somewhere.cm> wrote in
news:42427903@newsgroups.borland.com: 

> Hi,
> 
> It has been so long since I have used command line compiler that I am
> really puzzled as how one can actually use dcc32...
> 
> The reason I want to use dcc32 directly as opposed to the IDE is that
> I want to write a script that can generate a release version of my
> project whenever I need to, while using the IDE for my debug version.
> 
> In that respect, I have a MyProject.cfg file that, from what I
> understand, is the one that ought to contain the compiler's settings
> for my project. 
> 
> I was therefore under the impression that a simple:
> 
> dcc32 MyProject.dpr
> 
> would do the job, but I was wrong... If I do that, then the compiler
...