Add Dependency Build Instruction File Handling #116
Conversation
This file contains hidden or 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
Added the concept of a conventional dependency build file. These files are automatically included and processed by the dependency() function after the internal call to FetchContent_MakeAvailable() and therefore build files can be used, as opposed to the dependency configuration files, to adjust specific properties of the dependency target. Added the DEPENDENCY_BUILD_FILE function parameter to let the user define an alternative dependency build file. Signed-off-by: kilo52 <[email protected]>
kilo52
added
Improvement
Removed unnecessary variable path append. Signed-off-by: kilo52 <[email protected]>
Improved warning message. Signed-off-by: kilo52 <[email protected]>
Added more explanations about dependency build files. Signed-off-by: kilo52 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Improved the
dependency()CMake function.Adds the concept of a conventional dependency build file. These files are automatically included and processed by the
dependency()function after the internal call toFetchContent_MakeAvailable()and therefore build files can be used, as opposed to the dependency configuration files, to adjust specific properties of the dependency target.Adds the
DEPENDENCY_BUILD_FILEfunction parameter to let the user define an alternative dependency build file.