Changes between Version 3 and Version 4 of pm-project-config


Ignore:
Timestamp:
May 31, 2006 11:03:31 PM (14 years ago)
Author:
andreasw
Comment:

finished first draft

Legend:

Unmodified
Added
Removed
Modified
  • pm-project-config

    v3 v4  
    105105 1. ''Name of a C function in the library''.  This should be the name of a C function has should be defined in the library.  If the users uses the {{{--with-cpx-lib}}} flag, it is tested if this function is indeed available.  If not, the {{{configure}}} script with fail with an error message.  If this argument for the macro is omitted, this test is skipped.
    106106
    107 A user will have to either specify both {{{--with-libname-incdir}}} and {{{--with-libname-lib}}} flags, or none.  After successful completation of the tests, the link commands will be added to the automake output variable {{{ADDLIBS}}}.  Also,
     107A user will have to either specify both {{{--with-libname-incdir}}} and {{{--with-libname-lib}}} flags, or none.  After successful completation of the tests, the link commands will be added to the automake output variable {{{ADDLIBS}}}.  Also, the preprocessor macro {{{COIN_HAS_CPX}}} (where CPX is replaced by the abbreviation given to the macro) for the configuration header file and an Automake conditional with the same name are defined.
     108
     109== Generation of Links for Data Files ==
     110
     111Some unit test programs and example programs required input data files.  In a VPATH configuration (i.e., the compilation takes place in different directories from where the source files are) it is then important to make sure that links to those data files exist so that the program can be run in those directories.
     112
     113To this purpose, the '''AC_COIN_VPATH_LINK''' macro should be used for each such file.  An example of this section of the {{{configure.ac}}} file from the Volume project is
     114
     115{{{
     116##############################################################################
     117#                   VPATH links for example input files                      #
     118##############################################################################
     119
     120# In case this is a VPATH configuration we need to make sure that the
     121# input files for the examples are available in the VPATH directory.
     122
     123AC_COIN_VPATH_LINK(examples/VolUfl/ufl.par)
     124AC_COIN_VPATH_LINK(examples/VolUfl/data.gz)
     125AC_COIN_VPATH_LINK(examples/Volume-LP/data.mps.gz)
     126AC_COIN_VPATH_LINK(examples/Volume-LP/lp.par)
     127}}}
     128
     129== Project Specific Tests ==
     130
     131If you need to perform other tests, you might need to use further autoconf macros and/or write some {{{/bin/sh}}} code.  For this, please consult the [http://www.gnu.org/software/autoconf/manual/autoconf-2.59/ autoconf documentation].
     132
     133If you have questions or run into problems, you can send a message to the COIN BuildUtils mailing list (which has not yet been created...)