...
After changing into the build ecflow directory, the user has to run CMake with his/her own options. The command gives feedback on what requirements are fulfilled and what software is still required. Table below gives an overview of the different options of configure. The default (without any options) will compile a share library only and install it will install in /usr/local/.
cmake options | doc | default |
|---|---|---|
| CMAKE_INSTALL_PREFIX | where you want to install your ecflow | /usr/local |
| CMAKE_BUILD_TYPE | to select the type of compilation:
| Release |
| CMAKE_CXX_FLAGS | more flags for the C++ compiler | |
| ENABLE_SERVER | build the ecflow server | on |
| ENABLE_PYTHON | enable python interface | on |
| PYTHON_EXECUTABLE | Pyhon3. Path to python3 executable | |
| ENABLE_UI | enable build of ecflowUI (requires Qt) | on |
| CMAKE_PREFIX_PATH | use to provide path to dependent libraries which are installed in a non-system locations. | |
| ENABLE_GUI | enable build of ecflowview (requires X11 and motif) | on |
| ENABLE_ALL_TESTS | enable performance, migration, memory leak , and regression tests | off |
| ENABLE_SSL | Encrypted communication for user commands (experimental, from ecflow release 4.5.0). Please see: Open ssl for more details. | off |
| ENABLE_SECURE_USER | password based protection for user commands (experimental, from ecflow release 4.5.0) Please see: Black list file (experimental) for more details. | off |
| BOOST_ROOT | where to find boost ( if non-standard installation ) If not specified cmake will look for an environment variable of the same name. |
...