Fix CMake not obeying Python aliases #503
Merged
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
Quick fix here. I noticed that on Windows, even if you configure the python install manager to target a specific Python version, Mbed will still use the most recent version installed (which is often undesirable behavior). I believe that the same thing would happen on Linux, and it would not obey the
update-alternatives
setting.Setting these CMake config options seems to cause FindPython to prefer whichever version of Python is pointed to by the
python3
orpython
aliases (as long as it is in the needed version range), which is generally what you want.Impact of changes
Migration actions required
Documentation
None
Pull request type
Test results