...

• cmake (   install cmake   (sudo apt-get install cmake)).   Need at least cmake/3.13.4
• g++     (   install g++        (sudo apt-get install g++))   ecflow 5 series can only be built with C++14 or later  compilers. i.e. at the minimum gcc 6.3 or clang 6.0.
• Python 3(optional)
  

  If you intend to use ecFlow Python API, You will need to install Python. (install python-dev (sudo apt-get install python-dev))

  Please ensure that python is accessible on $PATH otherwise, you may need to customise $BOOST_ROOT/tools/build/v2/site-config.jam . 

  The python installation should include the development packages

  If you do not need the python apiAPI, then you can build without it, see below.
• Qt for ecFlowUI (Qt5 preferredmandatory).
  For self-installed Qt libraries, consider setting CMAKE_PREFIX_PATH (see below). See also http://doc.qt.io/qt-5/cmake-manual.html for further details.
• opensslOpenSSL(optional)
• sphinx(optional), this is used to generate ecflow python API

Setting up the build environment

• ecfFlow ecFlow consists of two tar files i.e.:  
  

  • boost_1_71_0.tar.gz (or any recent boost)

  • ecFlow-5.38.01-Source.tar.gz

    Create a directory for the build:

    Code Block
    language bash
    mkdir /tmp/ecflow_build

    
    

• Copy the the two tar file into this directory, then change directory to /tmp/ecflow_build

• Un-zip then un-tar the two file files:

  Code Block
  language bash
  tar -zxf boost_1_71_0.tar.gz tar -zxf ecFlow-5.38.01-Source.tar.gz

  
  

• You should have two directories created:

  Code Block
  boost_1_71_0 ecFlow-5.38.01-Source

  
  

• Create two environment variables. These are used by some of the scripts:

  Code Block
  export WK=/tmp/ecflow_build/ecFlow-5.38.01-Source export BOOST_ROOT=/tmp/ecflow_build/boost_1_71_0

  
  

• If you have a module system, please ensure that before you start, gccGCC,cmake,python3, etc are available in $PATH.

  Code Block
  language bash
  module load gnu module load cmake module load python3 module load qt

  
  

Build boost

In future releases of ecflow 5 series, the client/server versions of ecflow do not have to be built with the same boost version. This is because ecflow 5  now uses JSON for client/server communication.

• Boost uses bjam/b2 for building the boost libs.
  bjam source is available in boost, hence we first need to build bjam itself:

  
  

  Code Block
  language bash
  cd $BOOST_ROOT ./bootstrap.sh

  
  

• If you do not require the ecFlow python apiAPI, you can avoid building boost python libs by setting

  
  

  Code Block
  title Disable boost python, if ecflow PYTHON api not required
  export ECF_NO_PYTHON=1

  
  

            You will also need to disable python when building ecFlow.  See the instruction under cmake before calling $WK/build_scripts/boost_build.sh (see below)

• ecFlow uses some of the compiled libraries in boost. The following script will build the required lib’s and  and configure boost build according to your platform. 

  Code Block
  language bash title Build boost libraries including python3 used by ecflow.
  cd $BOOST_ROOT $WK/build_scripts/boost_build.sh # compile boost libs used by ecFlow. Please see notes in boost_build.sh, if you want to build both for python2 and python3

  
  

Build

cmake

As configure, CMake  CMake will run some tests on the customer's system to find out if required third-party software libraries are available and notes note their locations (paths). Based on this information it will produces produce the Makefiles needed to compile and install ecFlow

...

After changing into the build ecflow directory, the user  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  will install in /usr/local/.

The  C++  compilers are chosen by CMake. (This can be overwritten by setting the environment variables CXX on the command line before you call cmake, to the preferred compiler).

Further, the variable CMAKE_CXX_FLAGS can be used to set compiler flags for optimisation or debugging. 

cd $WK
mkdir build; cd build;

# Go with defaults, will build with CMAKE_BUILD_TYPE=Release and install to /usr/local
cmake .. 

# build release with debug info  
# cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo

# Override install prefix 
# cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local/apps/ecflow/5.38.01 

# do NOT build the gui.
# cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local/apps/ecflow -DCMAKE_BUILD_TYPE=Release -DENABLE_GUIUI=OFF

# ignore Wdeprecated-declarations compiler warning messages and do NOT build python api
# cmake .. -DCMAKE_CXX_FLAGS="-Wno-deprecated-declarations"  -DENABLE_PYTHON=OFF

# Use -j option to speed up compilation. Determine number of cpu's
CPUS=$(lscpu -p | grep -v '#' | wc -l)
make -j${CPUS}
make check
make install

cd $WK
rm -rf build
mkdir build; cd build
cmake ..      # or use whatever cmake configuration you used before

To use the ecFlow Python Api, you need to add/change PYTHONPATH. 

...

export PYTHONPATH=$PYTHONPATH:<prefix>/5.38.01/lib/python2python3.76/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/5.38.01/lib/python3.6/site-packages/ecflow 

...

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.

...

cd $WK/build  # change to the build directory
cmake -DCMAKE_INSTALL_PREFIX=/tmp/avi/custom/ecflow/5.38.01 -DCOMPONENT=python -P cmake_install.cmake -- make install  # install python module under /tmp/avi/custom/ecflow/5.38.01

ecflow_ui: Make a list servers accessible to all users

The GUI used by ecFlow is called ecflow_ui.  This is used to interact and visualize the ecFlow servers.

...

• creating a file called servers

• The format of the servers file is server's file is very easy:

  Code Block
  title server file format
  <server_name> <machine_name> <port>

  An example might be:

  Code Block
  title servers file
  server machineX 3141 projectX machineabc 4141 exp1 machineabc 4141 mars bigmac 11031

  
  

• Copy this file to CMAKE_INSTALL_PREFIX/share/ecflow/.   This makes the list of servers accessible to all users of ecflow_ui

  Code Block
  cp servers /tmp/avi/custom/ecflow/5.38.01/share/ecflow/.

  
  

Python API (from ecflow 5.6.0)

The most up to date python API documentation can be generated. This requires that sphinx-build is available on $PATH.

cd $WK
cd Doc/online
make clean; make html

The api can then be viewed in the browser. Please open file $WK/Doc/online/_build/html/index.html