...

./scripts/cmake-itm-marconi-gcc-74.sh

make -C build

make -C build install

* UDA-plugins: why do you use $HOME installed Boost (export BOOST_ROOT=/afs/eufus.eu/user/g/g2jhollo/boost_1_62_0)

- If I remember correctly, when I was developing one of the mapping plugins the version of Boost available on the gateway was too old, so I had to install my own. If a newer version of Boost is available this can be removed.

* UDA: what is a purpose of "$HOME/boost_1_62_0" dir?

- See previous answer.

* Are UDA-plugins based on specific version of UDA? or any version of UDA can be loaded?

...

To reiterate there is no run-time dependency on the data-dictionary (only access layer), but where mapping files exist I don’t think they have been updated since 3.28 or similar. Just to say that I don’t think the plugin version control tracks the DD version they are consistent with in any way. This means that we can compile today against 3.32 or whatever version we are at, (and the code will run without seg faulting or stack smashing or other library-mismatch errors you may see) but the data retrieval will fail as the mappings do not yet comply with the latest DD updates. Procedurally, perhaps there should be a step to confirm DD compliance of the mappings at each release too.

UDA install steps

1. Cloning repository
   1. git clone ssh://git@git.iter.org/imas/uda.git 
   2. cd uda
   3. git checkout tags/<tag_number> 
2. Building 
   1. env INSTALL=/gw/swimas/extra/uda/<tag_number>/gcc/4.8.5   ./scripts/cmake-itm-marconi-gcc-4.sh

   2. make -C build-gcc-4 

3. Installation

   1. make -C build-gcc-4 install

4. Setting system module (has to be done manually)

   1. copy existing module (e.g.  cp -r /gw/modules/lib/itm-boost/1.78.0   /gw/modules/lib/itm-boost/<installed version>)
   2. update versions etc
5. Setting pkg-config (has to be done manually)
   1. copy existing files (e.g.  cp -r /gw/switm/boost/1.78.0/gcc/4.8/lib/pkgconfig   /gw/swimas/extra/uda/<tag_number>/gcc/4.8.5/lib)
   2. update versions etc