cgal/Installation/config/support
Michael Hoffmann 537d560cce Also do single <-> multi-threaded for Windos. 2006-03-06 13:41:20 +00:00
..
README Fixed flag generation for testfiles. 2006-03-03 16:20:04 +00:00
S05-BOOST The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
S20-GMP Separate mpfr from gmp. 2006-03-06 08:08:17 +00:00
S21-GMPXX The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
S25-MPFR Separate mpfr from gmp. 2006-03-06 08:08:17 +00:00
S30-CORE The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
S32-CGALCORE Cleanup. 2006-02-28 16:00:43 +00:00
S60-LEDA The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
S62-LEDAMS The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
S80-QT3MT Also do single <-> multi-threaded for Windos. 2006-03-06 13:41:20 +00:00
S81-QT3 Also do single <-> multi-threaded for Windos. 2006-03-06 13:41:20 +00:00
S82-QT3MSMT Also do single <-> multi-threaded for Windos. 2006-03-06 13:41:20 +00:00
S83-QT3MS Also do single <-> multi-threaded for Windos. 2006-03-06 13:41:20 +00:00
test_BOOST.C The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
test_CORE.C The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
test_GMP.C The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
test_GMPXX.C The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
test_LEDA.C The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00
test_MPFR.C Separate mpfr from gmp. 2006-03-06 08:08:17 +00:00
test_QT.C The files for our new 3rd party lib support. 2006-02-27 19:42:44 +00:00

README

When adding a new file here:

 * Name it S??-x, where x is the (new) library you plan to support and
   ?? is a two-digit number between 00 and 99.

 * The name x consists of capital letters and digits only.

 * The number ?? indicates the (increasing) order in which compiler
   options are added to the compiler call; the smaller this number,
   the earlier the options appear. For linker options, this order is
   reversed.

 * Each file is lists a set of flags to enable support for a certain
   3rd party library. In our terminology, such a file is called a
   package, whereas the libraries are referred to as features. A
   package may provide any number of features. Vice versa, a feature
   may be provided by several packages; however, only one of the
   packages providing a feature may actually be used at the same time,
   that is, packages providing the same feature are implicitly in
   conflict to each other.

   Each file has the following entries.

   - PROVIDES: the feature(s) provided by it, separated by spaces.

   - DESCRIPTION: text, only used to distinguish from other packages
       which provide the same feature(s).

   - CXXFLAGS: compiler flags 

   - LDFLAGS: linker flags 

   - LIBS: list of libraries to link with, separated by spaces.

   - REQUIRES: list of features and/or variables required by the
     package. A required variable is prefixed by the string DOLLAR_,
     whereas features appear as-is. A package should only depend on
     features that appear before it in the (increasing) order of
     packages.

   - INCOMPATIBLE: list of features and/or variables incompatible with
     the package. An incompatible variable is prefixed by DOLLAR_,
     features appear as-is.

   - STDINCLDIRS: list of directories (separated by :) which may be
     package include dir (may contain wildcards, if
     backslash-escaped).

   - INCLTHING: a directory or file which has to be in the package
     include dir (may contain wildcards, if backslash-escaped). This
     is used to identify candidate dirs only.

   - STDLIBDIRS: list of directories (separated by :) which may be
     package lib dir (may contain wildcards, if backslash-escaped).

   - LIBTHING: a directory or file which has to be in the package lib
     dir (may contain wildcards, if backslash-escaped). This is used
     to identify candidate dirs only.
     
* Each feature should have a test program called test_name.C, where
name is the name of the feature. There are no test programs for
packages.

# EOF