-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify options for meson in pyproject.toml #108
Comments
That does sound like a reasonable feature request to me. It's not possible right now to do this in xref |
Based on ufo-kit/ufo-core#189 (comment), I think this doesn't necessarily need to live in @llohse does that work for you? |
Mhm, not really. What I have in mind is rather a convenience feature as follows. For example, consider a C/C++ library with optional python bindings. When installing the library via pep517, it would not make sense to compile it without the python bindings. It might be possible to implement this in meson.build by somehow detecting when being called by meson-python (although I would not know how) but I am not sure if that would be any cleaner. |
Ah okay, thanks for the clarification. It's clear to me now. So gh-122 is a prerequisite, but this makes sense as a follow-up. The interface should follow whatever comes out of gh-122. Something like [tool.meson-python]
setup-args = "-Doption=value"
install-args = "-Dother-option=other-value"
No, that seems worse. |
If you wanted to implement this, it would have to be for example using a |
Fixed in #167. |
Is it possible to specify options for meson in the pyproject.toml? If yes, could you document how?
Consider a project that has optional python bindings. I would need to enable them, when building via pip / pypa build.
mesonpep517 has
meson-options
that get passed to the meson call, but I could not find anything comparable in meson-python.The text was updated successfully, but these errors were encountered: