These release notes cover the changes made for the 2016-1 release, which covers:
In section Software provided with installers is provided further information about the following installers:
Section Cumulative changes and notes lists what we provide in the following git development branches:
Here is listed what software and respective versions are provided inside the binary installers, namely:
OpenFOAM 4.x, commit 7dfa780c481b8b79b1ee4d5bcf3e6b839a5ef017, 4th of August 2016.
ThirdParty 4.x, commit eb996b45f4ed40bd6c22a7c2f66a5f091e606f34, 3rd of August 2016.
The following list provides the changes cumulative with the already ones listed in previous release notes:
Switched from using MSys to using MSys2, as the main command line interface.
newWindow is new alias for starting a new window from within MSys2,
nonetheless, we can also use the key combination
Had to create a new script
translating path names for the mingw-w64 GCC compiler. Used in
Had to replace all entries of
off64_t, due to a crazy bug
in the compiler stack, where
off_t is somehow defined as
long int instead
Introduced a new script
wmake/scripts/makeObjectLongPath for translating
the object file paths to the long form when needed. Used in the
For some Git clients, the following is needed
git config --local core.longpaths true
Due to how long the file paths are becoming in OpenFOAM’s source code, we
need to use Windows’
subst command to define a drive letter where
blueCFD-Core will operate from. This affects only certain operations (when
building from source code), but installation can be made anywhere else.
Certain solvers have a rather steep cyclic dependency loop, which we had
to figure out a work-around for. This was first implemented in blueCFD-Core
multiphaseEulerFoam; now it has been
extended to support the
reactingEulerFoam solver stack as well.
We no longer need to rename files that have “Patch” in their name. This was
fixed in GCC+MinGW itself, as provided in MSys2, which embeds a default manifest:
Various MPI toolboxes are supported in varying degrees:
When building for the first time on a clean system with MS-MPI 7.1, it has to be installed on the system, otherwise it will not run as intended. It can be uninstalled afterwards, if you need to develop for multiple MS-MPI versions.
From our experience, MS-MPI versions are usually not compatible with each other, e.g. it is not possible to use the build with MS-MPI 2012 on a machine that has MS-MPI 7.1 installed globally.
It is unknown if MPICH2 can run on a machine that has MS-MPI installed.
Open-MPI does not interfere with MS-MPI nor MPICH2.
MPICH2 and Open-MPI are no longer developed/supported by their respective developers to run on Windows.
Only tested with 64-bit builds.
Metis 5.1.0 is supported and provided along with OpenFOAM 4.x in blueCFD-Core 2016-1, but it is not supported with OpenFOAM 3.0.x when blueCFD-Core 2016-1 was developed.
The command line in MSys2 now shows the current version/fork of OpenFOAM that is being used on that terminal. The idea was based on the example given here.
The Windows Command Line option has been removed (
removed), at least for the time being. There has been no clear feedback on
whether this is still needed or not. Nonetheless, we can bring it back if
people give us feedback on this.
A weird linking bug was worked-around to build
This hack will hopefully not be needed in future builds. The issue can
apparently pop up when building any other executable as well and this bug fix
does not seem to be applicable to those other occurrences.
foamList will give several error messages, but do not mind it much,
because it is due to duplicate entries that loading additional libraries will
lead to. Example:
Duplicate entry alphaContactAngle in runtime selection table fvPatchField We're sorry, but the application crashed and safe stack tracing isn't available in this current implementation of blueCFD-Core patches for OpenFOAM.
Ongoing development to have a faster and length-controllable test loop, extending beyond what OpenFOAM currently provides.
Integrated stack tracing is still not-operational within the ports released with blueCFD-Core 2016-1. Nonetheless, we’re aiming to have it operational in the next release.
The release notes for blueCFD-Core 2.3-1 and older versions are provided here: blueCFD-Core Release Notes