@@ -102,6 +102,12 @@ Define the flags used by the compiler to build the C++ source files. It is recom
Define the flags used by the compiler to build the C source files (GTest and {fmt}). It is recommended to use `-O2` or `-O3` level of optimizations, but it can be changed to match the compiler.
#### `CMAKE_INSTALL_PREFIX`
Default: SISSO++ Source Directory
Path to where the final library and executable files will be placed
### Installation Settings
#### `BUILD_PARAMS`
...
...
@@ -129,14 +135,10 @@ Default: OFF
If `EXTERNAL_BOOST` is ON then use the pre-built Boost Libraries currently in your path or in `$ENV{BOOST_ROOT}`
Here the `-O3` flag is for optimizations, it is recommended to stay as `-O3` or `-O2`, but it can be changed to match compiler requirements.
When building Boost from source (`EXTERNAL_BOOST OFF`) the number of processes used when building Boost may be set using the
`BOOST_BUILD_N_PROCS` flag in CMake. For example, to build Boost using 4 processes, the following flag should be included in the
`initial_config.cmake` file:
We recommend to use `-DEXTERNAL_BOOST=OFF` if you are building the python bindings with an anaconda environment or if you are using non-standard C++ or MPI libraries. If the boost libraries have already been built with the same C++ compiler, MPI library, and Python environment, then `EXTERNAL_BOOST=ON` can be used.
```
#set(BOOST_BUILD_N_PROCS 4 CACHE STRING "")
```
#### EXTERNAL_BUILD_N_PROCS
This flag will have no effect when linking against external boost, i.e. `EXTERNAL_BOOST ON`.
Default: 1
We recommend to use `-DEXTERNAL_BOOST=OFF` if you are building the python bindings with an anaconda environment or if you are using non-standard C++ or MPI libraries. If the boost libraries have already been built with the same C++ compiler, MPI library, and Python environment, then `EXTERNAL_BOOST=ON` can be used.
The number of processes passed to make when building external libraries.
