Build and Install

The installation described here is for UNIX platforms only.

The installation process is easy in the case you already have the required libraries and a standard configuration.

Required libraries

The first step of the installation is to make sure you have the required libraries. We have now a quite large set of libraries, we are trying hard to use well known and easy to install libraries but we must admit this could be a difficult task to install all by yourself...

The mandatory libs are Python, numpy, HDF5 and CHLone, VTK and Qt. The cython compiler and scons (for CHLone) are also required. Then, if you want to build CGNS.WRA (we recommend to do so), you need libcgns.

Warning

The libcgns (CGNS/MLL) is NOT required for pyCGNS. You need it if you want the WRA module, all other pyCGNS tools are using CHLone.

The complete set of required tools/modules/libraries contains Python, HDF5 and other graphical toolkits:

• Python (starting from v2.4)
• numpy (v1.1 +)
• cython (v0.16 +)
• hdf5 (v1.8.5 +)
• CHLone (v0.4 +)
• VTK (v5.8 +)
• Qt (v4.7 +)
• pySide (v4.7 +)

The VTK and the Qt graphical toolkits need to have a Python binding. The important point is to use the native Python binding of these toolkits, not any other (see installation details hereafter).

No Python binding is required for HDF5.

Optional libraries

The so-called mid-level library is not mandatory, the WRA module is the only one to have dependancies on.

• CGNS/MLL (libcgns) (starting v3.0)

Installation process

Once you have these installed you can proceed with pyCGNS. You go into the top directory and you edit the pyCGNSconfig.py.in (see Configuration file contents). You have to set the correct paths and various values such as directory search libs or flags.

Then you run:

python setup.py build

and then:

python setup.py install

or:

python setup.py install --prefix=/local/tools/installation

All the modules of the pyCGNS package are installed and you can now proceed with tutorial examples.

Single module installation

You can ask for a single module installation:

python setup.py build --single-module=MAP
python setup.py install

You have to check that this installation doesn’t overwrite an existing installation with the other pyCGNS modules.

Configuration file contents

The pyCGNSconfig_user.py should work with no modification if you have a standard installation. All you have to declare is the directory in which we can find Python/numpy/hdf5/CHLone/cgns libraries.

If you have specific installations you can change some paths/flags for each external library: hdf5, numpy, CGNS/MLL and CHLone. The configuration file is a Python file, it is imported after the default configuration. The changes you make in the configuration file will overwrite the defaults:

# --- stuff to add for HDF5

#HDF5_VERSION          = ''
HDF5_PATH_INCLUDES    = ['/home/myself/hdf5/include']
HDF5_PATH_LIBRARIES   = ['/home/myself/hdf5/lib']
#HDF5_LINK_LIBRARIES   = []
#HDF5_EXTRA_ARGS       = []

To avoid overwriting, use Python to update the config:

# --- stuff to add for HDF5

#HDF5_VERSION          = ''
HDF5_PATH_INCLUDES    = ['/home/myself/hdf5/include']
HDF5_PATH_LIBRARIES   = ['/home/myself/hdf5/lib']
#HDF5_LINK_LIBRARIES   = []
HDF5_EXTRA_ARGS       = HDF5_EXTRA_ARGS + ['-DMYFLAG']

You do not have to specify the VTK nor the Qt libraries, there is no direct link to these libraries: the Python modules will do that.

Module dependancies

The pyCGNS modules have dependancies with their brothers. The list below gives you the required modules (or optional) for each of them.

• MAP : None
• PAT : MAP
• WRA : PAT MAP
• APP : PAT MAP
• NAV : PAT MAP APP (WRA)

NAV depends

The CGNS.NAV tool uses two graphical toolkits, one for the GUI (Qt) and another one for the graphical view window (VTK). The VTK toolkit must have its Python binding installed. You should not use pyVTK but the native Python binding of VTK. To do so, edit the VTK configuration file to set the Python wrapping and all associated paths. And example of production could be:

cd VTK
mkdir B
cd B
cmake ..

Then edit the CMakeCache.txt file:

//Wrap VTK classes into the Python language.
VTK_WRAP_PYTHON:BOOL=ON

And build/install...

The Qt toolkit is used with the PySide Python binding, which is its official bindingwith this langage. We do not use pyQt. You can check you have the correct bindings by typing:

python
>>>import vtk
>>>import PySide

Both should not fail...

MAP depends

The CHLone librarie is required and thus HDF5 is required.

WRA depends

CGNS/MLL and CGNS/ADF libraries are required. Set the following variable to ON in the CMakeCache.txt file:

//Build the CGNSTools package
BUILD_CGNSTOOLS:BOOL=ON

//Build a shared version of the library
CGNS_BUILD_SHARED:BOOL=ON

//Enable or disable the use of Fortran
ENABLE_FORTRAN:BOOL=ON

//Enable or disable HDF5 interface
ENABLE_HDF5:BOOL=ON

The WRA and NAV modules (and CHLone by the way) are using cython. You can check your cython is present using:

cython --version

That should not fail...

Test

Some of the pyCGNS modules have embedded tests. Once you have installed pyCGNS, you can run each test suite from another user account/directory:

python -c 'import CGNS.MAP.test;CGNS.MAP.test.run()'

All modules tests can be run the same way, replace MAP by any of PAT, WRA, VAL, NAV, APP, DAT. You can run all the tests by importing CGNS.test:

python -c 'import CGNS.WRAP.test;CGNS.WRA.test.run()'
python -c 'import CGNS.PAT.test;CGNS.PAT.test.run()'

python -c 'import CGNS.test'

The tests are running silently, if there is a problem you would see a stack error on the output.