Page History

...

• Now make sure bjam is accessible from $PATH or use $BOOST_ROOT/bjam  in place bjam below.
• For installation the following environment variables are required.

  ECFLOW_INSTALL_DIR         # Directory Location for client ,server and gui program's
  ECFLOW_PYTHON_INSTALL_DIR  # Directory Location for ecflow python package
          

  The python installation can be customised, by changing Pyext/jamfile.jam and $BOOST_ROOT/tools/build/v2/site-config.jam

• We now need to build ecFlow. Currently ecflowview/GUI is only built if environment variable of name ARCH is set to linux:

  Code Block
  language bash
  cd $WK bjam variant=release

   

  On some systems like fedora/redhat you may run into compiler errors which complain about the template depth being exceeded. In this case compile using:

   

  Code Block
  language bash
  cd $WK bjam c++-template-depth=512 variant=release # using boost 1.53 with gcc 4.8, will have excessive warnings. To prune these warnings use bjam c++-template-depth=512 cxxflags=-Wno-unused-local-typedefs variant=release

   

  If you have a multi-core machine, you can speed up the build using,  the -j<n> option. Where ‘n’ is an integer, of the number of cores.

   

  Code Block
  language applescript
  CPUS=$(lscpu -p | grep -v '#' | wc -l) bjam variant=release -j${CPUS)

• Once ecFlow is built it can be installed.    NOTE, if you used c++-template-depth=512 || cxxflags=-Wno-unused-local-typedefs, use it again for the next step.

   

  Code Block
  language bash
  bjam variant=release install-all

   

  This will create directories:

  Code Block
  <ECFLOW_INSTALL_DIR>/bin <ECFLOW_INSTALL_DIR>/lib <ECFLOW_INSTALL_DIR>/doc <ECFLOW_INSTALL_DIR>/share <ECFLOW_PYTHON_INSTALL_DIR>

  Depending on your umask setting you may need to call chmod 755 on the executables

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

   

  Code Block
  language bash
  export PYTHONPATH=$PYTHONPATH:$ECFLOW_PYTHON_INSTALL_DIR

• When compiling ecflowview in a system where motif is not installed in the usual location, or where both motif and lesstif are installed, it is possible to export the environment variables MOTIF_INCLUDE and MOTIF_LIBRARY to help bjam to find the right location for include files and libraries.

  Openmotif may be retrieve from IST server and installed locally: wget http://www.ist-inc.com/motif/download/motif_files/openmotif-2.1.32-2_IST.x86_64.rpm rpm2cpio openmotif-2.1.32-2_IST.x86_64.rpm | cpio -idmv

  user shall then compile setting MOTIF_INCLUDE and MOTIF_LIBRARY variable.

  ecflowview

• By default the ecflowview 'server'

  and‘ecflowview

  and ‘ecflowview.menu’ files are placed in  <ECFLOW_INSTALL_DIR>/share/ecflow directory. However you can use ECFLOWVIEW_HOME shell variable to override this.

  
  The <ECFLOW_INSTALL_DIR>/share/ecflow/server files defines the list of servers you want all your users to see in ecflowview. If has a very simple format. For each ecflow server add a line like:

  Code Block
  <server_name> <machine_name> <port>

• ECFLOWRC variable may be set to use alternative directory for user ecflowview option files (default is $HOME/.ecflowrc)

...