5 | | A number of COIN projects that generated libraries have an {{{examples}}} subdirectory. After you run configure, you will find a simple {{{Makefile}}} in there, that has been adapted to your system. If you want to hook up your own code to this COIN library, it might be a good idea to start by looking at this Makefile. |
| 5 | Assume that you have dowloaded the package {{{Pkg}}} |
| 6 | in the directory {{{Coin-Pkg}}}. You have run {{{configure}}}, {{{make}}}, and {{{make install}}} from |
| 7 | the directory {{{Coin-Pkg}}}. Assume that you used {{{Coin-Pkg}}} as |
| 8 | the install directory (i.e. the default), obtaining a library |
| 9 | {{{Pkg.so}}} in {{{Coin-Pkg/lib}}} and include files in {{{Coin-Pkg/include}}}. |
7 | | {{{Note:}}} You should use only the libraries and header files that have been installed by {{{make install}}}, not from the source code directory from the COIN code. We are using the GNU autotools to compile the code, and picking up libraries and headers from the source directories has a good chance of creating problems. Similarly, you will have to do a {{{make install}} before you can compile the examples. |
| 11 | For most packages, the main directory contains an {{{examples}}} |
| 12 | subdirectory. Assuming that this is the case for the package {{{Pkg}}}, the directory {{{Coin-Pkg/examples}}} |
| 13 | contains a {{{Makefile}}} that has been adapted to your system. |
| 14 | If you want to hook up your own code to this COIN library, it might be a good idea to start by looking at this Makefile. |