6.4 Extending NEMO environment

Let us now summarize the steps to follow to add and/or create new software to NEMO. The examples below are suggested steps taken from adding Aarseth's nbody0 program to NEMO, and we assume him to have his original stuff in a directory /nbody0.

1:

Create a new directory, "cd $NEMO/usr ; mkdir aarseth" and inform the system manager of NEMO that a new user should be added to the user list in $NEMO/usr/Makefile. You can also do it yourself if the file is writable by you.

2:

Create working subdirectories in your new user directory, "cd aarseth ; mkdir nbody0".

3:

Copy a third level Makefile from someone else, and substitute the subdirectory names to be installed for you, i.e. your new working subdirectories ('nbody0' in this case): "cp ../pjt/Makefile . ; emacs Makefile".

4:

Go 'home' and install, "cd /nbody0 ; make install", assuming the Makefile there has the proper install targets. Check the target Makefile in the directory $NEMO/usr/aarseth/nbody0 what this last command must have done.

Actually, only step 1 is required. If a user cannot or does not want to confirm to the level 3/4 separation, he may do so, as long as the Makefile in level 3 (e.g. $NEMO/usr/aarseth/Makefile) contains the nemo_lib, nemo_bin and nemo_src install targets. An example of adding a foreign package that way is the GRAVSIM package , which has it's own internal structure. In the directory tree starting at $NEMO/usr/mbellon/gravsim an example of a different approach is given. Sometimes public domain packages have been added to NEMO, and its Makefiles have been adapted slightly to the NEMO install procedure.