Changes between Version 2 and Version 3 of user-compile


Ignore:
Timestamp:
May 28, 2006 12:58:45 PM (14 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • user-compile

    v2 v3  
    33These instructions only pertain to UNIX-like systems, where the {{{configure}}} scripts can be run.  If you want to use the MS Developer Studio to compile the code, please see the [http://projects.coin-or.org/MSDevStudio MSDevStudio project page].
    44
     5If you have problems, have a look at the [http://projects.coin-or.org/BuildTools/wiki/user-troubleshooting troubleshooting page.]
     6
    57== Compiling the Code ==
    68
    7 Assuming that the {{{configure}}} script ran successfully, you can compile the source code, including all subprojects, by typing
     9Assume that you have dowloaded the package {{{Pkg}}}
     10in the directory {{{Coin-Pkg}}} and that you have run {{{configure}}} with appropriate options successfully in
     11the directory {{{Coin-Pkg}}}.
     12
     13You can now compile the source code, including all subprojects, by typing in {{{Coin-Pkg}}}
    814
    915{{{
     
    1723== Testing the Compilation ==
    1824
    19 Most of the COIN packages provide a unit test (in the {{{test}}} subdirectory), which can be used to verify if the compiled code works correctly.  If you want to test the compilation for the main project only (i.e., {{{Clp}}} in our [wiki:user-directories example]) you type
     25Most of the COIN packages provide a unit test (in the {{{test}}} subdirectory), which can be used to verify if the compiled code works correctly.  If you want to test the compilation for the main project only (i.e., {{{Pkg}}} you type in {{{Coin-Pkg}}}
    2026
    2127{{{
     
    2329}}}
    2430
    25 If you want to run the tests for all subprojects (i.e., {{{CoinUtils}}} and {{{Clp}}} in our [wiki:user-directories example]), you can do that with
     31If you want to run the tests for all subprojects (e.g. {{{CoinUtils}}} and {{{Pkg}}}), type in {{{Coin-Pkg}}}
    2632
    2733{{{
     
    2935}}}
    3036
    31 This will run the unit test in all COIN projects that have one.
     37This will run the available unit test for {{{Pkg}}} and all other
     38downloaded packages.
    3239
    3340You don't need to type {{{make}}} before running {{{make test}}} or {{{make tests}}}.
     
    3542== Installing the Executables, Libraries and Header Files ==
    3643
    37 To install the final product of the compilation, i.e., the reason you are doing all this, you type
     44To install the final product of the compilation, i.e., the reason you are doing all this, you type 
    3845
    3946{{{
     
    4552In the {{{lib}}} directory you will also see {{{*_addlibs.txt}}} files (such as {{{clp_addlibs.txt}}}).  This contains a string with additionally required libraries (such as {{{-lz}}} if you are using the zlib GNU package), adapted to your system and configuration settings.  If you link with an installed COIN library, you should also specify the context of the corresponding {{{*_addlibs.txt}}} file in the link command.
    4653
    47 Some COIN projects come with examples that show how a generated library can be used.  In that case, in the {{{example}}} subdirectory for the project, you will find a simple Makefile to compile the examples, adapted to your settings.  If you want to link your own code with a COIN library, it is probably best to start with this Makefile; read more [wiki:user-examples  here].
     54Some COIN projects come with examples that show how a generated library can be used.  In that case, in the {{{examples}}} subdirectory for the project, you will find a simple Makefile to compile the examples, adapted to your settings.  If you want to link your own code with a COIN library, it is probably best to start with this Makefile; read more [wiki:user-examples  here].
    4855
    4956== Further Makefile Targets ==