Normally, typing ``make'' is all that is needed to install the package, provided that the gnu make is available through that command. Some variables might need to be defined, see the file INSTALL in the directory BAC. (When the location of files is mentioned below, the given path always starts implicitly from the directory BAC for files specific to the example or it starts with COIN for files related to COIN, BCP, or CLP.)
The file Makefile.bc has a line starting with ``USER_DEFINES = ''. Three flags can be put on this line :
The object files (*.o) and executable (bcps) are in a subdirectory of BAC whose name depends on your system. For this document, the name of this subdirectory is assumed to be SYST. If the flag(s) used are modified in the file Makefile.bc, make sure that the three files TM/BB_tm.cpp, LP/BB_lp.cpp, and Member/BB_init.cpp are recompiled. This can be achieved by touching these files or by removing the files BB_tm.o, BB_lp.o and BB_init.o (in the subdirectory SYST) before issuing the ``make'' command. (The first line of the output gives the flags that were used when compiling Member/BB_init.)
Once the program is compiled, it can be run either by typing ``./SYST/bcps'' or ``./SYST/bcps bb.par''. The second command makes the code read the parameter file bb.par. (Parameters will be discussed below in Section 8.) The obvious difference between the two commands is in the amount of output that is produced. The first command yields a detailed output. The second command prevents the code of diving and uses Depth-First-Search instead of Best-Bound in the selection of the next node to process.