Set to ON to include static versions of the library Set to ON to include shared versions of the library Set to ON to build extra examples for the library Set to ON to build benchmarks for the library Set to ON to build examples for the library Set to ON to build unit tests for the library The table below shows the current list of options, definition for the option, and a default value. What is built and what features are included/excluded.Įach of the options is enabled by saying -DOPTION_NAME=ON and is disabled by saying -DOPTION_NAME=OFF PALISADE is also exported as a CMake package for the benefit of any users wanting to use PALISADE the package files are also installed hereĭefault is to build PALISADE for release, with no debug information developers may want to specify -DCMAKE_BUILD_TYPE=Debugīeginning with release 1.10, the PALISADE build has a number of options to control Once this is done, make can be run inside of the build tree.
CMake will create a Makefile in the build tree. The source tree is passed to CMake as an argument on the command line. The project is described in files named CMakeLists.txt.ĬMake is run in the build tree. These should be different directories! The build tree can be in a subdirectory of the source directory (such as "build") or in some other place. The "source tree" is where the PALISADE source is located. The first step in using CMake is deciding where the build should be performed. This page describes how CMake is used in PALISADE, and how contributors should use CMake when adding new files or new components. PALISADE uses CMake to create the Makefiles that build and install the PALISADE Library.
0 kommentar(er)
