Switching to scikit-build-core instead of meson for building #215
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
|
@bd-j — I'm going to merge this because while we lose Windows builds, we get wheels for ARM macs, which I expect will be more useful (looking at the PyPI download stats!). |
|
awesome, thanks @dfm |
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.
There has been a lot of development one scikit-build-core, a CMake-based build backend for Python packages with good support for Fortran libraries. It's in much better shape than when I last looked and it seems more promising than meson to me. In particular, it should now support cross compilation. I started out just implementing this to learn about the developments, but I think it might actually be sensible to switch!