Fix python meta data generation
Summary
Several smaller changes to improve python meta data handling, see dune-grid#141 (closed).
Main changes
- Move
set(<module>_FOUND 1)
to the end ofdune_project()
- Add
set(HAVE_<MODULE> 1)
at the end offind_dune_project()
to provide the "dune-way" of indicating found packages - Collect all
HAVE_<MODULE>
flags for all dependencies in the python_cmake_flags
variable
Edited by Simon Praetorius
Merge request reports
Activity
assigned to @simon.praetorius
added 4 commits
- fa3dd8f6 - [cmake] define HAVE_{module} flags to check during cmake
- 780e2570 - [cmake] automatically add all found dependencies and suggestions to meta data
- 2bf8f9d5 - [cmake] automatically add DUNE_OPTS_FILE to python meta data
- be60661c - [cmake] define HAVE_${ProjecName} already during initialization
Toggle commit listmentioned in issue dune-grid#141 (closed)
- Resolved by Christian Engwer
- Resolved by Simon Praetorius
- Resolved by Simon Praetorius
There are some changes I have to test carefully. The changes might have consequences in other places than just the python meta-data.
mentioned in merge request dune-grid!560 (merged)
- Resolved by Christian Engwer
- Resolved by Christian Engwer
- Resolved by Simon Praetorius
- Resolved by Simon Praetorius
added 1 commit
- b191b5ea - [cmake] set _FOUND at the end of dune_project
added 1 commit
- e1b8287c - [cmake] set ${ProjectName}_FOUND at the end of dune_project
Please register or sign in to reply