...
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.
The naming convention for these architecture specific files is: <architecture>-<compiler>-<build type>.cfg. For example, the file fcmcfg/x86_64-gnu-opt.cfg would be for Linux 64bit with the GNU compilers and the optimized build.
How to change build type.
Before compiling the OpenIFS model, the build configuration must first be set by several environment variables:
...
FCM would then read the file fcmcfg/oifs.cfg which would expect to find a file called: darwin-intel-opt.cfg. This file would need to be created by the user.
Change compiler flags
All the compiler flags and options are contained in the build specific files (e.g. x86_64-intel-opt.cfg). As above a number of environment variables can be defined to override the default options set in these files.
Ways of working
Override compiler options for given .cfg files whilst testing and developing. Additional or personalized options once testing is finished can be set in new .cfg files - or - change the ones provided.
| 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> |
...