CMake - Add one CMakeLists per package #8265
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this version is copy-pastable
|
Instead of manually creating cmake scripts, can't we create custom targets in case we have |
|
I don't like much that option, because it forces to use the top-level CMakeLists, while the solution I suggested is "package-centered" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of Changes
To be able to test a full package (tests, examples, and if they exist benchmark and demo) at once, for example using
ctest(or simply compiling in visual studio), I suggest to add one CMakeLists per package, at the root of the package.This PR introduces two such CMakeLists, which I think are very handy.