Changes between Version 11 and Version 12 of ropp_repository

Timestamp:

2008-12-04T15:54:35Z (16 years ago)

Author:

Dave Offiler

Comment:

--

ropp_repository

@@ -34 +34 @@
 svn checkout https://svn.grassaf.org/ropp/ropp_test/tags/<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.
+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}}} only has tags set
+from ROPP release version 2.0.
 
 === Tags ===
@@ -54 +55 @@
 autoconf
 }}}
-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 configure.ac or Makefile.am template files, an {{{autoreconf}}} should be sufficient. The whole sequence needs to be re-run if any .m4 (macro) file is changed.
+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 {{{configure.ac}}} or {{{Makefile.am}}} 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 ===
@@ -62 +63 @@
 To add any new subroutine files to the build system it is necessary to update the {{{build/Makefile.am}}} 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 {{{Makefile.am}}} file in the appropriate subdirectory.
+All '.f90' and 'Makefile' files are included in 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 {{{Makefile.am}}} file in the appropriate subdirectory.
 
 Having edited {{{configure.ac}}} and or {{{Makefile.am}}} files, type {{{autorconf}}} to generate the corresponding {{{configure}}} or {{{Makefile.in}}} 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.