🚀 go-pugleaf

If the make file command line for bcc32.exe is like this:

.cpp.obj :
    bcc32 $(COMPILE_OPTIONS) {$< }

Then the {$< } will be expanded to a list of as many of the files which need 
to be compiled as will fit on a command line and only one instance of 
bcc32.exe will be loaded to compile all of them.

.cpp.obj :
    bcc32 $(COMPILE_OPTIONS) @&&|
{$< }
|

That should put the list of files into a temporary file (typically 
make@@@@.000) and temporary files used for redirection have no inherent 
limit on the number of file names as they are not command line limited.  I 
have used the "@&&|" many times but never in exactly this way so check if I 
am right on how make.exe will handle it.

> ... although I'd be happy with parsing XMLs, the BCB4- way is a makefile 
> format, that does not look as easy to parse...

It seems that I am always amazed by others' preferences.  If I had to quote 
a job with either XML or make file syntax as the input, my quote for XML 
would be much higher to reflect the extra work I felt it required.

The advantage of handling the project file yourself is that you then have 
the opportunity to handle frequently seen problem cases such as
  pathname\" >
,situations where the paths are so long they choke the IDE's build and cases 
where BCB6 builds reference VCL4.LIB (or whatever the name is) carried over 
by converting a project instead of recreating it when the user installs a 
new version.

.  Ed

> Jonathan Benedicto wrote in message
> news:43300a6b@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.