COMP: handle unset WM_OSTYPE for cmake targets (issue #909) (a410f52e) · Commits · Development / openfoam · GitLab

Skip to content

GitLab

Explore

Sign in
Register

Primary navigation

Project

openfoam
- Activity
- Members
- Labels
- Releases
- Service Desk
- Contributor analytics
- Model experiments

Snippets Groups Projects

Admin message

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Development
openfoam
Commits
a410f52e

Commit a410f52e authored 6 years ago by

Mark OLESEN

Downloads
- Patches
- Plain Diff

COMP: handle unset WM_OSTYPE for cmake targets (issue #909)

- regularise referencing of OpenFOAM env variables, sources etc.

parent df9c675c

Branches

Tags

No related merge requests found

Changes 5

Hide whitespace changes

Inline Side-by-side

Showing

applications/utilities/postProcessing/graphics/PVReaders/PVFoamReader/CMakeLists.txt 39 additions, 13 deletions

...Processing/graphics/PVReaders/PVFoamReader/CMakeLists.txt
applications/utilities/postProcessing/graphics/PVReaders/PVblockMeshReader/CMakeLists.txt 34 additions, 9 deletions

...ssing/graphics/PVReaders/PVblockMeshReader/CMakeLists.txt
src/functionObjects/graphics/runTimePostProcessing/CMakeLists-Common.txt 13 additions, 25 deletions

...ects/graphics/runTimePostProcessing/CMakeLists-Common.txt
src/functionObjects/graphics/runTimePostProcessing/CMakeLists-OpenFOAM.txt 32 additions, 0 deletions

...ts/graphics/runTimePostProcessing/CMakeLists-OpenFOAM.txt
src/functionObjects/graphics/runTimePostProcessing/CMakeLists.txt 3 additions, 3 deletions

...tionObjects/graphics/runTimePostProcessing/CMakeLists.txt

with 121 additions and 50 deletions

0% or .

You are about to add 0 people to the discussion. Proceed with caution.

Finish editing this message first!

Please register or sign in to comment