Building CGAL using the branch build presented here keeps the build-sources attached to the Git repository.
Note that we do not document here what are the dependancies and cmake options that are needed to configure CGAL as they are already documented in the installation manual.
The cmake script at the root of the repository is the one to use to build the CGAL library from a branch. It will collect the list of packages of the branch and will append their include folder to the include path. This is main noticable difference with a build using a regular flat release.
Here is an example of how to build the library in Debug:
git clone https://github.com/CGAL/cgal.git /path/to/cgal.git
cd /path/to/cgal.git
mkdir -p build/debug
cd build/debug
cmake -DBUILD_TYPE=Debug ../..
make
Here is an example of how to build the library in Release:
> git clone https://github.com/CGAL/cgal.git /path/to/cgal.git
> cd /path/to/cgal.git
> mkdir -p build/debug
> cd build/debug
> cmake -DBUILD_TYPE=Release ../..
> make
Note that no installation is required to use that version of CGAL once it has been compiled.
To compile a program using CGAL, simply set CGAL_DIR
to the location
of where you built the library (environment or cmake variable).
Here is an example of how to build in debug the examples from the 3D Triangulations package:
> cmake -DCGAL_DIR:PATH=/path/to/cgal.git/build/debug /path/to/cgal.git/Triangulation_3/examples/Triangulation_3
> make
If you're trying to build examples or tests that does not already have a CMakeLists.txt
, you can trigger its creation by calling the script cgal_create_cmake_script
found in /path/to/cgal.git/Scripts/scripts/
at the root of the example/test directory. Here is an example for the examples of the 2D Triangulation package:
> cd /path/to/cgal.git/Triangulation_2/examples/Triangulation_2
> /path/to/cgal.git/Scripts/scripts/cgal_create_cmake_script
> cd -
> cmake -DCGAL_DIR:PATH=/path/to/cgal.git/build/debug /path/to/cgal.git/Triangulation_2/examples/Triangulation_2
> make
A build may be outdated after an include/dir has been deleted, switched or even updated. This might lead to compile problems (link with outdated version). Thus, it is recommended to build CGAL after each update, switch, merge of a branch (in particular if directories have been added/deleted, or cpp files have been added, deleted or altered).