It is my intention to always have BCB6 spit out a make file. It should be compatible with the free Borland's free C++ compiler. The same version of make is used for both BCB5 and 6.
Don At 09:32 AM 2/15/2002 +0100, you wrote: >At 12:31 PM 14/02/2002 -0800, Tinny Ng wrote: >>As a general proposal, how about we exclude any out-dated project files like >>BCB4, Vacpp in the source package distribution but still leave them in CVS in >>case some users need them? It is confusing to ship some project files >>that are >>out-of sync with the source. >> >>Any comment? > >This makes perfect sense; it's better to omit them if they're known to be >broken. As a further note, it would be nice to also include >Makefile-versions of these project files. I mention this because some >people are possibly using the free(-ish) command-line tools, which don't >come with any way to build from the BCB project-files. Instead they come >with Borland's make tool. > >This shouldn't be too much effort because I believe there is a tool >included with BCB for generating makefiles that correspond to a BCB >project (BPR2MAK.EXE?). > >Just a suggestion, > > - Andrew > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
