fix: make FindPython2 and FindPython3 work #2662
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.
Description
When using FindPython3 (or FindPython2) from outside for a project that embeds the Python interpreter (with
pybind11:embed
), pybind11 isn't detecting Python correctly. This results in a working cmake execution, but with linking errors after building. FindPython is working though.This is due to wrong target names (e.g.
Python3::Python3
instead ofPython3::Python
) used inpybind11NewTools.cmake
.This was tested under Debian testing with an actual pybind11 git clone, cmake 3.16.3 and Python 3.8.5
Suggested changelog entry:
Close #2664