Make files

next - skip - up - start

I have included make files for a number of compilers. These provide an alternative way of compiling your programs than with the IDE that comes with PC compilers. See the files section for details. See the example for how to use them. Leave out the target name to compile and link all my examples and test files.

PC

I include make files for some of PC compilers I have access to. They all use the make utility that comes with the compiler. I don't know whether they work with versions of the compilers other than the ones I have. The make files for Borland need editing to show where you have stored your Borland compiler.

Unix

The make file for the Unix CC compilers link a .cxx file to each .cpp file since some of these compilers do not recognise .cpp as a legitimate extension for a C++ file. I suggest you delete this part of the make file and, if necessary, rename the .cpp files to something your compiler recognises.

My make file for Gnu GCC on Unix systems are for use with gmake rather than make. This defines BOOL_LIB so there is no need to do this in include.h. I assume your compiler recognises the .cpp extension. Ordinary make works with it on the Sun but not the Silicon Graphics or HP machines. On Linux use make.

My make file for the CC compilers works with the ordinary make.

To compile everything with the CC compiler use 

   make -f cc.mak
or for the gnu compiler use 
   gmake -f gnu.mak

There is a line in the make file for CC rm -f $*.cxx. Some systems won't accept this line and you will need to delete it. In this case, if you have a bad compile and you are using my scheme for linking .cxx files, you will need to delete the .cxx file link generated by that compile before you can do the next one.

next - skip - up - start