🚀 go-pugleaf

So have your program launch the compiler instead of launching make.exe.

Have your program write the set of options to a text file, perhaps 
TheOpts.cfg

Then create two text files, each of which has a space-delimited list of 
source files names.

Now have your program launch bcc32 twice in this way:

bcc32 +TheOpts.cfg @1stListFile.txt
bcc32 +TheOpts.cfg @2ndListFile.txt

Each instance of bcc32.exe will compile all files listed in the redirected 
text file whose name it is given.

It can check the return value from either instance of bcc32.exe and decide 
to then run or not run the linker (or use a make file for the linker).

.  Ed

> Jonathan Benedicto wrote in message
> news:432efb87$3@newsgroups.borland.com...
>
>> That is what makefiles are for.  Generate a makefile that contains all of
>> the files that you want to compile, and then launch the compiler once
>> specifying the makefile instead of any particular file.
>
> The problem with the makefiles is that I wanted to execute at least two 
> bcc32 instances in parallel, retrieiving the next file to be compiled from 
> a "pool" of files. So I built my program to basically be a interface 
> between make and bcc32, that took the file list that bcc32 was given, 
> stored it, and then ran two bcc32 instances passing each 1 file. As fast 
> as they finished compiling the file given, they were re-run with the next 
> file. This way twin processor machines were being used to their fullest 
> extent when compiling a BCB project.