Creation of a main pack

As an example, here is how to build the main pack of cycle 31T1 for the executables ALDODB, ODBTOOLS, IOASSIGN and BATOR :

% gmkpack -a -r31t1 -p aldodb/odbtools/ioassign/bator

/home/khatib/bin/gmkpack/util/gmkpack starts.
### configuration for main pack ###
Creating main pack 31t1_main.01.PGI616.x ...
Architecture file directory :
.gmkfile/
copy PGI.LXGMAP.x from directory /home/khatib/bin/gmkpack/arch
Programs system directories :
sys
Basic directories :
src
src/local
lib
bin
Unsatisfied external references directories :
src/unsxref/quiet
src/unsxref/verbose
Sources control directory :
src/.gmak
Sources view :
local
Projects directories :
src/local/sur
src/local/mpa
src/local/mse
src/local/xrd
src/local/tfl
src/local/tal
src/local/arp
src/local/ald
src/local/sat
src/local/odb
src/local/uti
src/local/bla
done.
Genesis :
/home/khatib/bin/gmkpack.6.3/util/gmkpack -r 31t1 -b main -a -l PGI616 -o x -p aldodb/odbtools/ioassign/bator

Prepare script(s) ...

>  copy compilation and load script on /home/khatib/pack/31t1_main.01.PGI616.x/ics_aldodb_etc ...
/home/khatib/bin/gmkpack/util/gmkpack ends.

GmkPack has created a main pack named 31t1_main.01.PGI616.x with a compilation script inside, named ics_aldodb_etc.

Remark : at this stage, the pack is empty, that is : it does not contain any source file.
The source code directories src/local/* have to be filled by yourself (for the time being there is no option in GmkPack to import source code).
Once the pack has been populated with source code you can submit or execute the compilation script :

./ics_aldodb_etc 2>&1 | tee ics_aldodb_etc.out

Here the output of ics_aldodb_etc is piped to tee in order to keep a logfile of the execution. If there is no batch scheduler in the machine, another way to do that is to mimic the behavior of a scheduler in a script like the one below :

if [ -f $HOME/.qsub ] ; then
  i=$(cat $HOME/.qsub)
else
  i=0
fi
i=$(($i+1))
echo $i > $HOME/.qsub
chmod 755 $1
time ./$1 2>&1 | tee $1.o$i

If everything works fine you should get at the end libraries in the directory lib and executables in the directory bin.

The installation of the full cycle 31T1 of ARPEGE/ALADIN/AROME/ODB (from the compilation of the source code to the link of libraries) takes about 90 minutes on a PC. The precise time depends on the processor, the compiler, the compilation options and the disks access velocity.