Changes between Version 3 and Version 4 of CompilingDynamico


Ignore:
Timestamp:
09/10/13 10:17:05 (11 years ago)
Author:
dubos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CompilingDynamico

    v3 v4  
    33== Generalities == 
    44 
    5 DYNAMICO is written in Fortran 90 with some legacy code in Fortran 77. 
     5DYNAMICO is written in Fortran 90 with some legacy code in Fortran 77. The build process is based on [http://metomi.github.io/fcm/doc/user_guide/make.html FCM]. 
    66 
    77== Prerequisites == 
     
    1212== Getting DYNAMICO through svn == 
    1313 
     14 
     15{{{ 
    1416svn co svn+ssh://mylogin@forge.ipsl.jussieu.fr/ipsl/forge/projets/dynamico/svn/codes/icosagcm/trunk DYNAMICO 
     17}}} 
    1518 
    1619'mylogin' should be your forge login. svn will create the DYNAMICO directory and download the source code there. 
     
    2023The compiling process is automated but some information is needed to guide it. This information is contained in text files in source:codes/icosagcm/trunk/arch . Sample files corresponding to a few machines (Ada at IDRIS, Curie at TGCC) are present. Assuming you compile on Ada : 
    2124 
     25{{{ 
    2226cd DYNAMICO 
    23 ./make_icosa -arch X64_ADA -parallel mpi -prod -jobs 8 
     27./make_icosa -arch X64_ADA -parallel mpi -prod 
     28}}} 
    2429 
    2530will compile DYNAMICO. The make_icosa script accepts keyword-value pairs which drive its behaviour. The most important option is arch=ARCH (here ARCH=X64_ADA). It directs make_icosa to use the information contained in : 
    26 * arch/arch-ARCH.env 
    27 * arch/arch-ARCH.fcm 
    28 * arch/arch-ARCH.path 
     31 * arch/arch-ARCH.env 
     32 * arch/arch-ARCH.fcm 
     33 * arch/arch-ARCH.path 
    2934 
    3035The *.env file is a shell script that is executed by make_icosa. It sets up the environment for use by *.path. *.path defines paths to libraries and modules needed for compilation. *.fcm defines the commands used to compile, link, etc. as well as options to be passed to the compiler/linker . 
     36 
     37After a successful build the main executable is found in the bin/ directory. 
     38