Build bundle of base packages for MAGIC and JEDI application
Tested compilers include:
- GCC 7.3.0, 7.4.0
- Intel 17.x.y.z
Required dependencies:
- NetCDF (Fortran and CXX API)
- CMake
- ecbuild
- eckit
- fckit
- ATLAS
- SABER
- OOPS
- IODA
- UFO
MAGIC employs an out-of-source build/install based on CMake.
Make sure the ecbuild executable script is found ( which ecbuild ).
# 1. Clone the MAGIC-bundle
git clone https://github.com/aerorahul/magic-bundle.git
cd magic-bundle
# 2. Create the build directory and cd into it:
mkdir /path/to/build
cd /path/to/build
# 3. Run ecbuild:
ecbuild /path/to/magic-bundle
# 4. Compile / Install
make -j 10
make installExtra flags maybe added to ecbuild in step 3 to fine-tune configuration.
-
--build=DEBUG|RELEASE|BIT--- Optimisation level- DEBUG: No optimisation (
-O0 -g) - BIT: Maximum optimisation while remaning bit-reproducible (
-O2 -g) - RELEASE: Maximum optimisation (
-O3)
- DEBUG: No optimisation (
-
compilers can be selected with
-DCMAKE_CXX_COMPILER=/path/to/gcc-7.2/bin/g++
The ecbuild command in step 3 will clone all the source code for the JEDI and MAGIC project defined in the
CMakeLists.txt in the bundle and the make command in step 4 will build them all.
For testing (from build directory):
ctestThe CMakeLists.txt file in this directory contains the list of the repositories included
in the bundle and the branch to be used. The branch specified in the CMakeLists.txt is
the one that will be compiled. When working with you own branch, the should be changed in
the CMakeLists.txt file but it is not necessary to re-run ecbuild, make is enough.
After the fisrt build, changes in the code can be tested by re-running only (from build directory):
make -j4
ctestBy default, make will not update you 510B r local repository from the remote. To update all repositories in the bundle, run:
make updateThe update will fail for repositories that contain uncommited code. This is a safety mechanism to avoid losing your work.