🚀 go-pugleaf

"Ed Mulroy" <dont_email_me@bitbuc.ket> wrote in message 
news:432fe843@newsgroups.borland.com...
> I understood you to have said just the opposite and to have asked how to 
> make make.exe do what you want.

Sorry for the confusion. Make does the makefile parsing for me, checks the 
dependancies, finds out what files must be compiled, and collates the 
compiler options. All of this my app then takes, and, depending on the 
options sent to it, loads 2 or more bcc32 instances to compile the project.

What I wanted is possibly a way to be able to load bcc32 into RAM, saving 
it from being loaded and unloaded everytime it completed a compiling 
operation, making the build faster.

> Make has no facilities for apportioning source files among compiler 
> instances executing in different threads.

This is why I had to add my app in between make and bcc32.

> However the IDE provides a *.bpr project file in which the names and 
> options for the various needed tools as well as the list of files used to 
> perform the build.  At least as I understand the concept it does not seem 
> to be that complicated to use the information from the project file and 
> then build the program in the way which you want.

One of the reasons that I don't want to go this way, is that BCB5+ uses a 
different project file format than BCB4-. And although I'd be happy with 
parsing XMLs, the BCB4- way is a makefile format, that does not look as 
easy to parse.

Jonathan