Changes between Version 14 and Version 15 of pm-project-config


Ignore:
Timestamp:
Aug 24, 2011 5:00:39 PM (8 years ago)
Author:
lou
Comment:

editorial changes

Legend:

Unmodified
Added
Removed
Modified
  • pm-project-config

    v14 v15  
    8080}}}
    8181
    82 Here, for each group of COIN-OR projects that is required to compile the libraries and programs in this project (including unit tests and example programs), we list their names as the argument of an invocation of '''AC_COIN_CHECK_PACKAGE'''.  This example is taken from Cbc.
     82Here, for each group of COIN-OR projects that is required to compile the libraries and programs in this project (including unit tests and example programs), we list their names as arguments of an invocation of '''AC_COIN_CHECK_PACKAGE'''.  This example is taken from Cbc.
    8383
    8484The arguments have the following meaning:
    8585
    86 1. The first argument is the '''name of the "package"''', which can consist of multiple COIN-OR projects. In this example, one defines a "package" {{{CoinDepend}}} which consists of !CoinUtils, Osi, and Clp, and make the configuration bail out when any component of the package is not present. This mechanism is meant for cases in which a project is not useful by itself, but only in combination with others.
    87 1. The second argument are the '''names of the pkg-config files associated with the projects that make up the package''', with the optional ability to specify specific required versions (see example below).
    88 1. The third argument can be used to specify particular libraries or binaries to which the particular dependency applies, in this case {{{CbcLib}}} and {{{CbcGeneric}}}.[[BR]]
     861. The first argument is the '''name of the "package"'''. A package can consist of multiple COIN-OR projects.
     871. The second argument specifies the '''names of the pkg-config files associated with the projects that make up the package''', with the optional ability to specify specific required versions. In this example, "package" {{{CoinDepend}}} is defined to consist of !CoinUtils, Osi, and Cgl. The configuration will bail out if any component of the package is not present. This mechanism is meant for cases in which a project is not useful by itself, but only in combination with others.
     881. The third argument can be used to specify particular libraries or binaries to which the dependency applies, in this case {{{CbcLib}}} and {{{CbcGeneric}}}.[[BR]]
    8989  The '''compiler and linker flags for the package are then accumulated''' in corresponding variables that can be used in Makefiles. In the example, variables {{{CBCLIB_CFLAGS}}}, {{{CBCLIB_LIBS}}}, {{{CBCGENERIC_CFLAGS}}}, and {{{CBCGENERIC_LIBS}}} are setup that contain the compiler linker flags for using both packages !CoinDepend and Clp.[[BR]]
    9090  The possibility to give specify several libraries or binaries in the third argument is for cases where the project exports both a library and a binary executable and these have different dependencies. In this case, different command lines are built up for each of them separately.