-
Notifications
You must be signed in to change notification settings - Fork 69
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
import('pkgconfig').generate()
generates wrong Meson introspection data
#609
Comments
You need to use |
I am running into this issue again.
It seems some targets, like |
I think it's worth going through all the more advanced/niche Meson target types and checking how they land in
I bet if we look at other things that aren't normally included in wheels (e.g., |
So: not really a bug, more a missing feature. |
Wheels cannot contain symlinks AFAIK. |
This would be a bug in Meson. |
Yet:) Being heavily discussed right now. Either way, silently omitting them is probably not the ideal way of handling this now. Also |
|
Sure, but that doesn't quite apply to this situation. It could be as complete as possible as the metadata encoding scheme allows for. I'd suggest to consider these Meson bugs, and once they're included in |
py.install_sources
import('pkgconfig').generate()
is not compatible with installing the result into a Python package
import('pkgconfig').generate()
is not compatible with installing the result into a Python packageimport('pkgconfig').generate()
generates wrong Meson introspection data
Reproducible: #608
install_data
here is just an example, I know I can usepy.install_sources
, but that is not viable in various different scenarios. In my case, I ran into it when usingimport('pkgconfig').generate(..., install_dir: py.get_path('purelib') / ...)
.The text was updated successfully, but these errors were encountered: