- in addition to managing different vendors and versions, it may also
be necessary or desirable to have a particular variant
(eg, profiling, release, etc).
Devise a new meaningful name for the variant and create a
corresponding wmake rule.
Eg, SYSTEMOPENMPI-profiling with a corresponding
"wmake/rules/linux64Gcc/mplibSYSTEMOPENMPI-profiling" file
that has suitable content for your system.
CONFIG: intel-mpi use intel64/ paths only for config and wmake rules (#1153)
- previously adjusted the config files, but missed the changes
required for the wmake rules too.
Now simply migrate to using "intel64/{include,bin,lib}"
instead of the older naming "{include,bin,lib}64"
These changes work since at least intel-mpi 2015 (5.x), but possibly
earlier as well
OpenFOAM Configuration
The main OpenFOAM settings are located in the parent etc/ directory.
Both POSIX (bash, dash,...) and csh shells are supported.
To configure OpenFOAM, source either the etc/bashrc or the
etc/cshrc file, as appropriate for your shell.
These source the following files in the config.sh/ or
config.csh/ directories:
setup: finalize setup of OpenFOAM environment (called by bashrc,cshrc)settings: core settingsaliases: aliases for interactive shellsunset: sourced to clear as many OpenFOAM environment settings as possiblempi: MPI communications library settingsparaview: application settings for ParaViewscotch: application settings for compiling against scotchmetis: application settings for compiling against metis
The config.*/example directories contain additional example configuration
files for the corresponding shell:
compiler: an example of fine tuning ThirdParty compiler settingsopenmpi: an example of fine tuning openmpi settings for OpenFOAMparaview: an example of chaining to the standard config/paraview with a different ParaView_VERSIONprefs: an example of supplying alternative site-defined settings