...
...
...
...
...
Column | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
|
...
...
...
...
...
...
...
...
...
...
Config files and variables
The FCM software uses configuration files identified by the suffix '.cfg'. They can be found in the directory oifs/make/fcmcfg
. The master configuration file for OpenIFS is in fcmcfg/oifs.cfg. It sets general configuration options for FCM, lets FCM know where the source code is and reads a single architecture and compiler specific configuration file. No compiler options are contained in the oifs.cfg file - these are always in the architecture specific configuration files.
...
...
...
...
...
...
...
changes the build type to the 'optimized' build. This means instead the file 'fcmcfg/x86_64-gnu-opt.cfg
' will be included by fcmcfg/oifs.cfg
instead of the file fcmcfg/x86_64-gnu-noopt.cfg.
...
export OIFS_BUILD=opt
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Recommendations
As described above, the build environment uses 3 types of build:
- Optimised
- Non-optimized
- Full debugging (nansC)
The compilation of OpenIFS can be changed is several ways:
...
For temporary changes when testing or debugging, setting environment variables (2) to override the compiler options is perhaps the simplest.
Once testing is finished and permanent changes are required, or if unsupported compilers are required, then copy an existing .cfg file and create your own. Any names can be used. For instance, if you wanted to have 2 configurations for the Intel compiler, one with the Intel MPI, the other with OpenMPI, then create files: x86_64-intel_impi-opt.cfg and x86_64-intel_ompi-opt.cfg and use the environment variable OIFS_COMP to switch between them. e.g. OIFS_COMP=intel_ompi (it's up to the user whether they want to create .cfg files for each build type; 'opt', 'noopt', 'nansC').
HTML |
---|
<script type="text/javascript" src="https://software.ecmwf.int/issues/s/en_UKet2vtj/787/12/1.2.5/_/download/batch/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector.js?collectorId=5fd84ec6"></script>
|
...