To get/compile NEMO standalone with esm_master we need to set the target directory to where a NEMO configuration is cloned to. In the current setup esm_master assumes that "destination" entry is used as both as the target directory for a "git clone ... AND the top level directory.
I introduced clone_destination (better names suggestions are highly appreciated) as an extra flag to allow setting the git clone destination differently than the top level directory.
Maybe this problem doesn't exist if NEMO standalone is integrated differently in the tools, but I currently don't know how to do that better.
To get/compile NEMO standalone with esm_master we need to set the target directory to where a NEMO configuration is cloned to. In the current setup
esm_master
assumes that "destination" entry is used as both as the target directory for a "git clone ... AND the top level directory. I introducedclone_destination
(better names suggestions are highly appreciated) as an extra flag to allow setting the git clone destination differently than the top level directory. Maybe this problem doesn't exist if NEMO standalone is integrated differently in the tools, but I currently don't know how to do that better.