Page History

<div class="section" id="install">
<span id="index-0"></span><span id="id1"></span>
<ul>
<li><p class="first">dependencies</p>
<blockquote>
<div><ul class="simple">
<li>python, 2.1-2.7,  Python 3.0 not tested.
If you intend to use ecFlow Python api, You will need to install python
If python installed in non standard installation, you may need to
customise $BOOST_ROOT/tools/build/v2/site-config.jam</li>
<li>Xlib for <a class="reference internal" href="/wiki/display/ECFLOW/Glossary#term-ecflowview"><em class="xref std std-term">ecFlowview</em></a></li>
</ul>
<p>ecfFlow consists of two tar files:</p>
<ul class="simple">
<li><tt class="file docutils literal"><span class="pre">boost_1_45_0.tar.gz</span></tt></li>
<li><tt class="file docutils literal"><span class="pre">ecflow_1_9.tar.gz</span></tt></li>
</ul>
</div></blockquote>
</li>
<li><p class="first">Create a directory for the build:</p>
<div class="highlight-python"><pre>&gt; mkdir /tmp/ecflow_build</pre>
</div>
</li>
<li><p class="first">Copy the the two tar file into this directory, then change directory to <tt class="file docutils literal"><span class="pre">/tmp/ecflow_build</span></tt></p>
</li>
<li><p class="first">Un-zip then un-tar the two file files:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="c"># gunzip boost_1_45_0.tar.gz</span>
<span class="c"># gunzip ecflow_1_9.tar.gz</span>
<span class="c"># tar -xf boost_1_45_0.tar</span>
<span class="c"># tar -xf ecflow_1_9.tar</span>
</pre></div>
</div>
</li>
<li><p class="first">You should have two directories created:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="n">boost_1_45_0</span>
<span class="n">ecflow_1_9</span>
</pre></div>
</div>
</li>
<li><p class="first">Create two environment variables. These are used by some of scripts:</p>
<div class="highlight-python"><pre>&gt; export WK=/tmp/ecflow_build/ecflow_1_9
&gt; export BOOST_ROOT=/tmp/ecflow_build/boost_1_45_0</pre>
</div>
</li>
<li><p class="first">Boost uses bjam for build.  ecFlow use bjam for build and installation
bjam source is available in boost, hence we first need to build bjam itself:</p>
<div class="highlight-python"><pre>&gt; cd $BOOST_ROOT
&gt; ./bootstrap.sh</pre>
</div>
<p>Now make sure bjam is accessible from $PATH</p>
</li>
<li><p class="first">Ecflow uses some of compiled libraries in boost. The following script
will build the required lib&#8217;s, in both debug and release forms:</p>
<div class="highlight-python"><pre>&gt; cd $BOOST_ROOT
&gt; $WK/build/build_boost.sh</pre>
</div>
</li>
<li><p class="first">We now need to build ecFlow:</p>
<div class="highlight-python"><pre>&gt; cd $WK
&gt; bjam variant=release</pre>
</div>
<p>If you have a multi-core machine, you can speed up the build using:
the -j&lt;n&gt; option. Where &#8216;n&#8217; is an integer, of the number of cores.</p>
<p>bjam variant=release -j4</p>
</li>
<li><p class="first">Once ecFlow is built it can be installed. This requires the specification
of two environment variables:</p>
<div class="highlight-python"><pre>ECFLOW_INSTALL_DIR          # Directory Location for client ,server and gui program's
ECFLOW_PYTHON_INSTALL_DIR   # Directory location for ecFlow python extension

Once these variable have been defined installation is done by calling::

bjam variant=release install</pre>
</div>
</li>
<li><p class="first">To use the <a class="reference internal" href="/wiki/display/ECFLOW/ecFlow+Python+Api#python-api"><em>ecFlow Python Api</em></a>, you need to add/change PYTHONPATH and LD_LIBRARY_PATH:</p>
<div class="highlight-python"><pre>export PYTHONPATH=$PYTHONPATH:$ECFLOW_PYTHON_INSTALL_DIR
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ECFLOW_PYTHON_INSTALL_DIR</pre>
</div>
</li>
</ul>
</div>