> I'm studying the same book, but I am using BC++ 1.0 and I went back to
> try building from both the IDE and from the command line.  Both worked,
> however the make function itself didn't work, so I compiled and linked
> separately from the command line ... sigh: something else to look into.

Just thought I'd mention that ftp.cdrom.com finally put my bake utility
into an actual directory other than incoming.  (pub/os2/dev32).  You might
want to try it.  After using bake for a few days, just the SIGHT of a make
file will give you the creeps.

The syntax of a bake file:

output.exe
source1.cc
source2.cc
source3.cc
source4.def

That's basically it.  The first line is what you're making (it knows how to
make .exe, .dll, and .lib files, and will figure out which you want from
the extension of the file).  The rest are source files (and it can take c
files, c++ files, .def, .rc, .obj, .res...  If you want to link with
non-standard libraries, just list them with a .lib extension.)

It can also handle the unix emulation capabilities of emx.  (if the target
ends in .emx it will compile an emulated unix .exe.)

Bake will resolve the dependencies for you and everything.  (It knows how
to parce C files, .def files, and .rc files to find #included files.  Does
it recursively even.)

I'm currently working on bake v2.00, which will have a configuration file
that allows you to define new file types for it.  (Use different compilers.
 Handle SOM.  All sorts of stuff.)  This one I'll probably release the
source code to under the GNU license.  We'll see.

Rob
 
--- Xblat