Changes between Initial Version and Version 1 of Ticket #541


Ignore:
Timestamp:
01/26/12 18:39:53 (12 years ago)
Author:
arango
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #541

    • Property Resolution → Done
    • Property Status new → closed

  • Ticket #541 – Description

    initial v1  
    1 The ROMS '''makefile''' is very powerful and complex.  Since all the algorithms are distributed in several sub-directories. Each sub-directory has it own library, which is used during the linking stage.  We need to account for the circularity of these objects in the libraries.  For instance, the ROMS/Utility codes ('''libUTIL.a''') uses modules located in other directories.  Therefore, in the '''makefile''' the includes the libUTIL.a at the beginning and end of the '''libraries''' list token. For example, in nonlinear model algorithms, we have:
     1The ROMS '''makefile''' is very powerful and complex.  All the ROMS algorithms are distributed in several sub-directories. Each sub-directory has it own library, which is used during the linking stage.  We need to account for the circularity of these objects in the libraries.  For instance, the ROMS/Utility codes ('''libUTIL.a''') uses modules located in other sub-directories.  Therefore, in the '''makefile''' we have the libUTIL.a at the beginning and near the end of the '''libraries''' list token. For example, in nonlinear model algorithms we have:
    22{{{
    33  libraries  := $(SCRATCH_DIR)/libUTIL.a
    … …  
    1010}}}
    1111
    12 It turns out that with some compiler version and computers operating systems we also need circularity in the '''modules''' token for the '''ROMS/Nonlinear''' directory modules:
     12It turns out that with some compiler versions and computers operating systems we also need circularity in the '''modules''' token for the '''ROMS/Nonlinear''' directory modules:
    1313
    1414{{{