Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Development
openfoam
Commits
bc51349d
Commit
bc51349d
authored
Dec 11, 2019
by
Mark OLESEN
Browse files
CONFIG: bump API to 1912 (pre-release)
- update repository links
parent
ef592894
Changes
3
Hide whitespace changes
Inline
Side-by-side
META-INFO/api-info
View file @
bc51349d
api=191
0
patch=
191111
api=191
2
patch=
0
README.md
View file @
bc51349d
...
...
@@ -39,9 +39,9 @@ Violations of the Trademark are monitored, and will be duly prosecuted.
If OpenFOAM has already been compiled on your system, simply source
the appropriate
`etc/bashrc`
or
`etc/cshrc`
file and get started.
For example, for the OpenFOAM-v19
06
version:
For example, for the OpenFOAM-v19
12
version:
```
source /installation/path/OpenFOAM-v19
06
/etc/bashrc
source /installation/path/OpenFOAM-v19
12
/etc/bashrc
```
# Compiling OpenFOAM
...
...
@@ -121,8 +121,8 @@ These 3rd-party sources are normally located in a directory parallel
to the OpenFOAM directory. For example,
```
/path/parent
|-- OpenFOAM-v19
06
\-- ThirdParty-v19
06
|-- OpenFOAM-v19
12
\-- ThirdParty-v19
12
```
There are, however, many cases where this simple convention is inadequate:
...
...
@@ -130,7 +130,7 @@ There are, however, many cases where this simple convention is inadequate:
operating system or cluster installation provides it)
*
When we have changed the OpenFOAM directory name to some arbitrary
directory name, e.g. openfoam-sandbox19
06
, etc..
directory name, e.g. openfoam-sandbox19
12
, etc..
*
When we would like any additional 3rd party software to be located
inside of the OpenFOAM directory to ensure that the installation is
...
...
@@ -150,18 +150,17 @@ when locating the ThirdParty directory with the following precedence:
2.
PREFIX/ThirdParty-VERSION
*
this corresponds to the traditional approach
3.
PREFIX/ThirdParty-vAPI
*
allows for an updated value of VERSION,
*eg*
,
`v19
06
-myCustom`
,
*
allows for an updated value of VERSION,
*eg*
,
`v19
12
-myCustom`
,
without requiring a renamed ThirdParty. The API value would still
be
`19
06
`
and the original
`ThirdParty-v19
06
/`
would be found.
be
`19
12
`
and the original
`ThirdParty-v19
12
/`
would be found.
4.
PREFIX/ThirdParty-API
*
this is the same as the previous example, but using an unadorned
API value. This also makes sense if the chosen version name also
uses the unadorned API value in its naming,
*eg*
,
`19
06
-patch190131`
,
`19
06
.19W03`
`19
12
-patch190131`
,
`19
12
.19W03`
5.
PREFIX/ThirdParty-common
*
permits maximum reuse for various versions, but only for
experienced user who are aware of potential version
incompatibilities
*
permits maximum reuse for various versions, for experienced user
who are aware of potential version incompatibilities
If none of these directories are found to be suitable, it reverts to
using PROJECT/ThirdParty as a dummy location (even if the directory
...
...
@@ -174,7 +173,7 @@ side-effects. In the above, the following notation has been used:
| PROJECT |
`$WM_PROJECT_DIR`
| The OpenFOAM directory |
| PREFIX |
`dirname $WM_PROJECT_DIR`
| The OpenFOAM parent directory |
| API |
`foamEtcFiles -show-api`
| The api or release version |
| VERSION |
`$WM_PROJECT_VERSION`
| The version we
'
ve chosen |
| VERSION |
`$WM_PROJECT_VERSION`
| The version we
ha
ve chosen |
To reduce the potential of false positive matches (perhaps some other
software also uses ThirdParty-xxx for its naming), the directory test
...
...
wmake/rules/General/general
View file @
bc51349d
#-------------------------------*- makefile -*---------------------------------
WM_VERSION
=
OPENFOAM
=
191
0
WM_VERSION
=
OPENFOAM
=
191
2
AR
=
ar
ARFLAGS
=
cr
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment