Skip to content
Snippets Groups Projects
Commit b5cddf43 authored by BLANCO-GARCIA's avatar BLANCO-GARCIA
Browse files

adds buildtracy.sh for sumo-metis and the CCRT

parent 4fb3ce54
No related branches found
No related tags found
No related merge requests found
echo "moving to Numerical Recipes"
cd nrecipes/recipes_c-ansi/
echo "cleaning Numerical Recipes"
make clean
echo "compiling Numerical Recipes"
export LANG=C
# export NUM_REC=/ccc/cont003/home/soleil/nadolskl/codes/nrecipes/recipes_c-ansi
export NUM_REC=$PWD
module load intel/20.0.4
module load gnu/11.1.0
module load mpi/openmpi/4.0.5 #for compatibility with currect elegant module
# compile the library in subdirectory lib
make -j
echo "moving to tracy 3"
cd ../../TracyIII/trunk/
echo "setting up the environment"
source set_var-topaze.sh
echo "make tracy 3 mpi"
bash make_for_tracy3.sh mpi
cd ../../
echo "creating build dir"
echo " cleaning old build"
rm -rf build
mkdir build
echo " copying compiled files with cp -rfP to keep symbolic links"
cp -rfP TracyIII/trunk/tracy/build/* TracyIII/trunk/tracy/tools/soltracy build
cd build
echo "linking psoltracy3 and psoltracy"
ln -s psoltracy3 psoltracy
cd ..
echo "soltracy and psoltracy done, enjoy !"
echo "Adios 8D"
echo "o"
echo "Compiling Tracy"
echo "Setting up common modules"
#module load intel/Compilers/2017.2.174
#module load intel/Compilers/2019.3.199
# 2022/mars
#module load openmpi/4.1.1
#2022/avril/28
#module load intel/Compilers/2017.2.174
#module load openmpi/4.1.1
#module load gcc/9.2.0
# 2023/jun/01 moving to modules in tools for sumo and sumo-metis compat
ml purge
#module load intel/Compilers/2017.2.174
module load tools/openmpi/4.1.1
module load tools/gcc/9.2.0
echo "seting up environment variables"
source set-vars-sumo-metis.sh
echo "moving to Numerical Recipes"
cd nrecipes/recipes_c-ansi/
echo "cleaning Numerical Recipes"
make clean
echo "compiling Numerical Recipes"
# compile the library in subdirectory lib
make -j
echo "moving to tracy 3"
#cd ../../TracyIII/trunk/
cd ../../tracy3/
echo "setting up the environment"
source set_vars_for_tracy3-sumo-metis.sh
echo "make tracy 3 mpi"
bash make_for_tracy3.sh mpi
cd ../
echo "creating build dir"
echo " cleaning old build"
rm -rf build
mkdir build
echo " copying compiled files with cp -rfP to keep symbolic links"
# cp -rfP TracyIII/trunk/tracy/build/* TracyIII/trunk/tracy/tools/soltracy build
echo "here"
pwd
cp -a tracy3/tracy/build/* tracy3/tracy/tools/soltracy build
cd build
echo "linking psoltracy3 and psoltracy"
ln -s psoltracy3 psoltracy
cd ..
echo "soltracy and psoltracy done, enjoy !"
echo "Adios 8D"
echo "o"
......@@ -9,10 +9,23 @@
# lack of a git repository for the external libraries, we will need to get a
# copy from Laurent Nadolsky.
# There two main parts :
- numerical recipes (ask Laurent)
- tracy3 (on gitlab)
If you have numerical recipes and tracy inside the same folder, you could just
copy 'buildtracy.sh' to that folder and launch it. There is one for sumo-metis
and one for the CCRT.
The first time 'buildtracy.sh' is launch it might stop due to a problem with
make distclean inside make_for_tracy3.h. My advice is to comment that line
in the first compilation, which would reset the project, and decomment that line
for the next compilations.
The goal with 'buildtracy.sh' is to produce a folder called 'build' with the
binaries for a new module.
Most of the time the above is enough. However, here below there is more detail.
I have added a script 'set-vars-sumo-metis.sh' that creates few environment
variables that are common to both numerical recipes and tracy3
during compilation.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment