mirror of https://github.com/CGAL/cgal
<CGAL/Double_map.h> is faster if Boost.Bimap is used. |
||
|---|---|---|
| .. | ||
| README | ||
| S05-BOOST | ||
| S06-BOOST_PROGRAM_OPTIONS | ||
| S07-BOOST_BIMAP | ||
| S15-X11 | ||
| S20-GMP | ||
| S21-GMPXX | ||
| S23-MPFR | ||
| S30-CORE | ||
| S32-CGALCORE | ||
| S40-ZLIB | ||
| S41-ZLIBMS | ||
| S45-APPLEVECLIB | ||
| S46a-SUNPERFORMANCECC | ||
| S46b-SUNPERFORMANCEGCC | ||
| S47-SGICOMPLIB | ||
| S48a-MKL64 | ||
| S48b-MKL32 | ||
| S49a-MKLWIN64 | ||
| S49b-MKLWIN32 | ||
| S50a-ACML | ||
| S50b-ACMLWIN | ||
| S52-BLASIFORTATLAS | ||
| S53-BLASGCCATLAS | ||
| S54-BLASWINATLAS | ||
| S55a-REFBLASGCC | ||
| S55b-REFBLASLINUXGCC | ||
| S55c-REFBLASSHARED | ||
| S56-REFBLASWIN | ||
| S58-LIDIA | ||
| S60-LEDA | ||
| S61-LEDA5X | ||
| S62-LEDAMS | ||
| S63-LEDA5XMS | ||
| S64-LEDAWIN | ||
| S65-LEDAWINMS | ||
| S70-OPENGL | ||
| S71-OPENGL_W32 | ||
| S72-LAPACK | ||
| S74-LAPACKWIN | ||
| S75-REFLAPACKLINUXGCC | ||
| S76-REFLAPACKWIN | ||
| S80-QT3MT | ||
| S81-QT3ST | ||
| S82-QT3MSMT | ||
| S83-QT3MSST | ||
| S91-TAUCSWIN | ||
| S92-TAUCS | ||
| S93-TAUCSFREEBSD | ||
| S96-TAUCSDARWIN | ||
| S98-TAUCSIRIXCC32 | ||
| S99-TAUCSIRIXCC64 | ||
| test_BLAS.cpp | ||
| test_BOOST.cpp | ||
| test_BOOST_BIMAP.cpp | ||
| test_BOOST_PROGRAM_OPTIONS.cpp | ||
| test_CORE.cpp | ||
| test_GMP.cpp | ||
| test_GMPXX.cpp | ||
| test_LAPACK.cpp | ||
| test_LEDA.cpp | ||
| test_LEDAWIN.cpp | ||
| test_LIDIA.cpp | ||
| test_MPFR.cpp | ||
| test_OPENGL.cpp | ||
| test_QT.cpp | ||
| test_TAUCS.cpp | ||
| test_X11.cpp | ||
| test_ZLIB.cpp | ||
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.
* Pay attention: If the name of a package x is a prefix of the name
of another package y, then x should appear before y in the
(increasing) order. For instance, GMP has number 20 which is
smaller than the number 21 of GMPXX.
* 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.
- COMPILETESTFLAGS: compiler flags that need to be used only during
the tests
* 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