...
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, regression tests. | 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. |
...
| Code Block | ||
|---|---|---|
| ||
export PYTHONPATH=$PYTHONPATH:<prefix>/4.1.0/lib/python2.7/site-packages/ecflow # If you used the default's then <prefix>=/usr/local # otherwise you should use whatever you entered for -DCMAKE_INSTALL_PREFIX, hence in the examples above we would have: export PYTHONPATH=$PYTHONPATH:/usr/local/apps/ecflow/4.1.0/lib/python2.7/site-packages/ecflow |
Installing Python to a custom directory
The default install for ecflow, will install python(if it was enabled) under the directory given to CMAKE_INSTALL_PREFIX.
However sometimes we may need to install the ecflow python module to a different prefix.(starting with release 4.13.10)
This can be done using:
| Code Block |
|---|
cd $WK/build # change to the build directory cmake -DCMAKE_INSTALL_PREFIX=/var/tmp/avi/custom -DCOMPONENT=python -P cmake_install.cmake -- make install # install python module under /var/tmp/avi/custom |
...