Root directory of your Boost installationĭirectory containing the boost/version.hpp fileĭirectory containing the compiled Boost librariesįull pathname to a release build of the compiled 'xyz' Boost libraryįull pathname to a debug build of the compiled 'xyz' Boost library VariableīOOST_ROOT The environment variable can be spelled either BOOST_ROOT or BOOSTROOT For example, you can add the path to the Boost. dll files are found by the dynamic linker, at run time. On Windows, if you link with Boost shared libraries, you must ensure that the. You can set the variable CGAL_Boost_USE_STATIC_LIBS to ON if you want to link with static versions explicitly. You can also provide the full pathname to a specific compiled library if it cannot be found in the library directory or its name is non-standard.īy default, when Boost binary libraries are needed, the shared versions are used if present. If it is not, you can specify the header and library directories individually. In most cases, if Boost is not automatically found, setting the BOOST_ROOT variable is enough. Version 1.69 and Earlier Warning If you have a version of Boost greater than 1.69 already installed on your system, and you want to configure and compile with an earlier version of Boost, then you will need to set the CMake variable Boost_NO_BOOST_CMAKE to ON (otherwise the FindBoost.cmake module of CMake will start searching for BoostConfig.cmake, and ignore the BOOST_ROOT variable). For example if you manually installed Boost 1.77 with -prefix=, then you should set Boost_DIR=/lib/cmake/Boost-1.77.0. Starting from Boost 1.70, the cmake config mode can be used for configuring the Boost version to use by setting the environment variable Boost_DIR to the path containing the file BoostConfig.cmake. Keep in mind that you must provide one or the other but never both. Since 3rd-party libraries are system wide, many of the CMake variables listed below can alternatively be given as similarly-named environment variables instead. This is indicated by a value ending in NOTFOUND. CMake automatically searches for dependencies so you need to specify these variables if CMake was unable to locate something. The following variables provide information about the availability and location of the 3rd party libraries used by CGAL. Variables Providing Information About 3rd-Party Libraries Variables Used Only When Building Programs (Such as Demos or Examples) Variableįull-path to the binary directory where CGAL was configured Whether to build shared or static libraries. Possible values are 'Debug' or 'Release'įull-path to the executable corresponding to the C compiler to use.įull-path to the executable corresponding to the C++ compiler to use. Note that the default build type is Debug, which should only be used to debug and will serverly limit performances. The following variables can be used to add flags without overriding the ones defined by cmake. The variables that correspond to both debug and release builds are always used in conjunction with those for the specific build type. If you provide your own definition for a variable, you will entirely override the list of flags chosen by CMake for that particular variable. Have in mind that these variables specify a list of flags, not just one single flag. Each variable holds a space-separated list of command-line switches for the compiler and linker and their default values are automatically defined by CMake based on the target platform. The following variables specify compiler and linker flags. The following boolean variables indicate which CGAL components to configure and/or build. Unless indicated differently, all the variables summarized below are CMake variables. They are given in the command line to CMake via the -D option, or passed from the interactive interface of cmake-gui. Most configuration variables are not environment variables but CMake variables. Summary of CGAL's Configuration Variables We however recommend using the graphical interface ( cmake-gui). This page lists CMake variables which you can use to help CMake find missing dependencies while using the command line.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |