...
| Code Block | ||
|---|---|---|
| ||
export PYTHONPATH=$PYTHONPATH:<prefix>/4.5.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.5.0/lib/python2.7/site-packages/ecflow |
Installing ecflow 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.3.0)
This can be done using:
| Code Block |
|---|
cd $WK/build # change to the build directory cmake -DCMAKE_INSTALL_PREFIX=/var/tmp/avi/custom/4.7.0 -DCOMPONENT=python -P cmake_install.cmake -- make install # install python module under /var/tmp/avi/custom/4.7.0 |
ecflow_ui: Make a list servers accessible to users
The gui use by ecflow is called ecflow_ui.
...
This is used to interact and visualize the servers.
You can make the list of server available for your users by:
- creates a file file called servers
The format of the server file is very easy:
Code Block title server file format <server_name> <machine_name> <port>An example might be:
Code Block server_name machineX 3141 projectX machineabc 4141 exp1 machineabc 4141 mars bigmac 11031Copy this file to:
Code Block # cp servers CMAKE_INSTALL_PREFIX/share/ecflow/. cp servers /var/tmp/avi/custom/4.7.0/share/ecflow/.