or CPT's wonderful journey through the installer towards getting IMAS on new platforms.

Disclaimer: all example steps given below are assuming BASH being your shell of choice.

1. IMAS

1.1. Installing main dependencies

Follow the list of requirements/dependencies as stored in https://git.iter.org/projects/IMAS/repos/access-layer/browse/README.md

Add modules to set them up in the environment.

1.2. Getting the IMAS installer

Clone the installer using either master (recommended) or develop branch (at your own risk)

git clone ssh://git@git.iter.org/imas/installer.git

1.3. Configuring

Create target directory where all IMAS related tools will be deployed (will be referenced as IMAS_HOME from now on).

Adapt site-config/Makefile.default to the local configuration and needs. Look at tools/imas-config.in to try to guess how to name your own site-config file, and/or check which files are being targeted by running

DEBUG=1 ./tools/imas-config.in

Check if configuration is generating the expected setting for the targeted DD and AL tags by running

make cache
make help TAG_DD=a.b.c TAG_AL=x.y.z

1.4. Building and installing

After making sure that compile time required modules are loaded, simply run, for given DD and AL versions

make install TAG_DD=a.b.c TAG_AL=x.y.z

2. IDStools

2.1. Getting the sources

Clone the idstools repo (from IMAS Core project, not from IMAS Extra...), and checkout the targeted tag

git clone ssh://git@git.iter.org/imas/idstools.git
cd idstools
git checkout x.y.z

2.2. Configuring

Create site-config file with same name used for the installer, and specify there the name of the IMAS module and the targeted idstools module name.

Make sure you have IMAS module loaded before attempting the build (it sets required IMAS_HOME variable and imas-config-installer).

Check if configuration is well set by checking the result of

make help

2.3. Building and installing

make all
make install

3. FC2K

3.1. Installing main dependencies

Requires ant and JaxFront

3.2. Getting the sources

Clone the fc2k repo from IMAS extra project, and checkout the targeted tag

git clone ssh://git@git.iter.org/imex/fc2k.git
cd fc2k
git checkout x.y.z

3.3. Configuring

Create two config files under the config directory:

config/install_xxxx.xml will contain information for building/installing fc2k
config/settings_xxxx.xml will contain information required when using fc2k to build actors

Once these files have been created, use imas-config-fc2k command to check if correct settings file is detected. For install file, link the one created as config/install_default.xml (or how to force ant to use the xxxx one, so we can avoid obtaining a "-dirty" version?).

Check configuration by

ant check-config

3.4. Building and installing

After making sure IMAS module is loaded

ant compile
ant install

4. XMLlib

4.1. Getting the sources

Clone the xmllib repo from IMAS libraries project, and checkout the targeted tag

git clone ssh://git@git.iter.org/lib/xmllib.git
cd xmllib
git checkout x.y.z

4.2. Configuring

Make sure autoconf / automake are available, then

./bootstrap 
./configure FC=<targeted fortran compiler, e.g gfortran> CC=<associated C compiler, e.g gcc> --prefix=<install_dir, e.g $IMAS_HOME/extra/xmllib>

4.3. Building and installing

make clean
make all
make check
make install

Then repeat the configuration and building/installing steps for each fortran compilers.

Associated module needs to be created manually

5. GGD

5.1. Getting the sources

Clone the ggd repo from IMAS extra project, and checkout the targeted tag

git clone ssh://git@git.iter.org/imex/ggd.git
cd ggd
git checkout x.y.z

5.2. Configuring