Replace $<CONFIG> in IMPORTED_LOCATION #459
Merged
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
Users might define an OUTPUT_DIRECTORY containing $<CONFIG>. Copying the byproducts works fine, but for the imported location we need to replace the genex. This is possible, since in single config mode we know the config, and in multi config mode we know the config for the `_CONFIG` variants of IMPORTED_LOCATION.
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.
Users might define an OUTPUT_DIRECTORY containing
$<CONFIG>. Copying the byproducts works fine, but forthe imported location we need to replace
the genex. This is possible, since in
single config mode we know the config,
and in multi config mode we know the
config for the
_CONFIGvariants of IMPORTED_LOCATION.Fixes #453