docs: Updates for building an extension with meson #1050
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
|
This looks great - thanks for your contributions @hpkfft |
|
Shall I merge this PR? it is still labeled as "draft". |
|
Yes, please merge at your convenience. |
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.
@WillAyd, I changed the C++ source code suffix to
cppsimply to be consistent with the rest of the nanobind docs. I'm not trying to impose my convention on others. :)Debian 12 (bookworm, the current stable version) includes meson 1.0.1, which is sufficient for building non-stable-ABI python extensions, but using the keyword argument
limited_apirequires meson 1.3.0. This is why I includedmeson.buildin full for building against the python stable ABI.I'll leave this PR as a draft until mesonbuild/wrapdb#2104 is merged in case additional changes are advisable.
Regards,
Paul