Changes between Version 19 and Version 20 of user-configure


Ignore:
Timestamp:
Jun 12, 2006 1:08:32 AM (14 years ago)
Author:
andreasw
Comment:

added explicit warning that configure has to be run from the base directory

Legend:

Unmodified
Added
Removed
Modified
  • user-configure

    v19 v20  
    1212Before you can compile the source code using {{{make}}}, the Makefiles have to be created, so that they contain the correct compiler names and options, as well as other system dependent information.  To this purpose, the {{{configure}}} shell scripts in the package's base directory (e.g., {{{Coin-Clp}}}) and in the projects' main directories (such as {{{Coin-Clp/Clp}}}) perform a number of tests and create the final Makefiles.  In addition, a {{{configure}}} script usually creates a header file (such as {{{Coin-Clp/Clp/inc/config_clp.h}}}) for the individual project, which contains {{{#define}}}s to help the source code to adapt to different platforms.
    1313
    14 To run the configuration scripts, you go into base directory of the downloaded COIN package (e.g., {{{Coin-Pkg}}}), and type
     14To run the configuration scripts, you go into the '''base directory''' of the downloaded COIN package (e.g., {{{Coin-Pkg}}}), and type
    1515
    1616{{{
    1717./configure
    1818}}}
     19
     20'''Note:''' You should run the {{{configure}}} script always from the base directory, not from a project subdirectory (such as {{{Coin-Clp/Clp}}}); the latter usually doesn't work.
    1921
    2022This picks default settings for compilers and compiler options.  You can change some aspects of the configuration by providing arguments to the configuration script, as described below.