Version 11 (modified by frhl, 12 years ago)

Update instructions to developers adding new routines

The ROPP Repository

The whole ROPP development system is divided into four areas:

  • ropp_src : Deliverable code & supporting development system
  • ropp_bld : Configure & build support scripts, distro builder etc
  • ropp_doc : User and project documentation
  • ropp_test : Test Folder (test system and its results)

The repository for ROPP can be accessed via the Subversion server at the URL

For a complete list of Subversion commands see the  SVN reference manual

Checking out trunk

To  checkout the latest development (trunk) versions:

svn checkout  ./trunk 
svn checkout  ./trunk
svn checkout  ./trunk 
svn checkout ./trunk

This will check out the source code, build support, documentation, and test folder, respectively to the local working directory.

Checking out old release versions

To checkout the older (tagged) release versions:

svn checkout<ver>  ./<ver>
svn checkout<ver>  ./<ver>
svn checkout<ver>  ./<ver>
svn checkout<ver> ./<ver>

This will check out the tagged source code, build support, documentation, and test folder, respectively to the local working directory. Here, <ver> is the tagged release version, e.g. 1.1, 2.0 etc. Note that ropp_bld is relatively new and does not currently have any tags set.


A  tag is just  copy or snapshot of a a particular revision of the repository. In the case of ROPP, a copy taken from the head of trunk at the time that the distribution files for a release were built. You could just as well checkout the revision number instead, but a tag is easier to remember!


Developments to ROPP should be made from, and committed to, a  branch rather than directly to the latest trunk version. This allows changes to be tested before merging the required changes back into the trunk. The trunk therefore represents a stable 'next potential release' state for ROPP. Branches can be temporary and might be for working on resolving a specific Trac Ticket.

Instructions for developers working with branches in ROPP are available  here.

Preparation for building

Having checked out ropp_src (trunk, tag or branch) some commands need to be run to locally create intermediate configuration and make files not in the repository, before the configure / make / make install sequence can begin:

aclocal -I m4 --force
automake -a -c

These commands need to be repeated in each of the ropp_tools, ropp_io etc modules. Thereafter, if any changes are made to the low-level or template files, an autoreconf should be sufficient. The whole sequence needs to be re-run if any .m4 (macro) file is changed.

Developing new code

In order to add a new sub-directory to the ROPP build system within a module it is necessary to edit the AC_CONFIG_FILES list of sub-directory Makefiles in the top-level file. It is also necessary to update the SUBDIRS list of subdirectories in the top-level file.

To add any new subroutine files to the build system it is necessary to update the build/ file by defining a list of subroutines with a suitable collection name and then adding the collection name to the libropp_<modname>_a_SOURCES list. If any new F90 modules are to be built, the module names should be added to the MODULES listing.

All '.f90' and 'Makefile' files are built as part of the ROPP distribution as default. In order to include other files (e.g. data files) within the ROPP distribution, it is necessary to explicitly define these as EXTRA_DIST within the file in the appropriate subdirectory.

Having edited and or files, type autorconf to generate the corresponding configure or scripts. In order to generate the updated Makefile script it is necessary to run configure, usually from a compiler-specific configuration file with the appropriate compiler flag settings and library paths.