Let normal variables take precedence over option()-declared variables
#37
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
Owner
|
Thank you for the PR! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This sets the CMake Policy 0077 to
NEWbehavior, allowing existing normal variables to not be overridden byoption()calls. I would like to have this; otherwise older versions of CMake build the Lua compiler/standalone interpreter when I explicitly tell it not to withset(LUA_BUILD_BINARY OFF)andset(LUA_BUILD_COMPILER OFF).An example from the GitHub Actions
ubuntu-latestrunner:(I don't want this building since it's being built for a platform it'll never run on...)