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.
As I was playing with CMake build process, I found that
scikit-build
folks have their own python build backend.I tried to switch to it and I think I'm successful at it, I think. It must be done with
project.toml
so I switched the meta data over to it from the cfg file.One thing I haven't achieved is to support the dynamic version data with their method. I poked around their website for a bit and came away not sure what to do (as I forgot 99% of how CMake works...) Here is the info, as limited as it may be:
https://scikit-build-core.readthedocs.io/en/latest/faqs.html#dynamic-setup-py-options
For now, I've relegated to
setuptools
by using the alternate build-backendscikit_build_core.setuptools.build_meta
, which if I understand correctly takes the info from the good ol'setup.py
.Donno if you are interested in updating this part of the project, but if you are, you can use this as a spring board.