Hi David, > From: David Sugar > Sent: Thursday, August 25, 2005 05:05 > To: Conrad T. Pino > Cc: Bug Common C++ > Subject: Re: Win32 - Borland C++ Builder 6.0 Compiles Fails > > This sounds good too! I know we had in the past a few people using bcc, > which is where the Makefile for Borland originally came from, but they > had not submitted updates in recent times. I do think supporting many > different compilers (beyond gcc) is very useful as a matter of principle > as each is able to identify a different set of problems and the result > is better quality code. Hmm...I guess that means I will need to add > Borland support and Makefiles to some of the other cc libraries as well...
Early Borland compilers used a single "makefile" for both command line and IDE builds but that hasn't been true for quite a while. I edited "Makefile.bcc" and got it working again. I'd like to commit Borland IDE project files also. IDE project files make command line make files redundant but we can continue providing them by using the IDE's "Export makefile..." function. The downside is the IDE build files may not be compatible with earlier Borland compiler versions. The same may be true of make file exports. IMO adding new compiler specific IDE build files can't hurt. Let's update "Makefile.bcc" with some hand editing to make it work as it once did but let's not go beyond that. If more command line make files are required then I can export them as "Makefile.bc6" or some other extension so that it's clear they are compiler version specific. Best regards, Conrad Pino _______________________________________________ Bug-commoncpp mailing list Bug-commoncpp@gnu.org http://lists.gnu.org/mailman/listinfo/bug-commoncpp
