Skip to content

Conversation

@sp1ritCS
Copy link
Contributor

See #14930, #14865

The gobject-introspection subproject just registers g-ir-scanner as a
python script, with meson unaware of the native module the script
depends upon that has to be built first. This patch works around this
issue by adding an the gobject-introspection-1.0 dependency (which
indirectly depends on the native module) if g-ir-scanner was overriden
by the g-i subproject.
This was added on dcbaker request[0], but doesn't actually work the way
we need it too, as meson always has too assume the tools from the
pkg-config file are build machine tools.

[0]:mesonbuild#14422 (comment)
@sp1ritCS sp1ritCS requested a review from jpakkane as a code owner August 20, 2025 10:07
@bonzini bonzini added this to the 1.10 milestone Aug 20, 2025
@bonzini
Copy link
Collaborator

bonzini commented Oct 31, 2025

@sp1ritCS please rebase

@sp1ritCS
Copy link
Contributor Author

sp1ritCS commented Nov 1, 2025

It might make sense to yield this until #15101 is merged and revisit this to see if (a subset of) it is still needed. I haven't verified it, but based on testing with #15101, its very possible that the only reason this PR worked is due to g-ir-scanner/g-ir-compiler picking up GIRs from the system installation, even tho they don't match the target architecture.

I guess that won't happen in the current release cycle, given that you and @xclaesse are currently busy with the rust/cargo stuff, but its going to be better that way.

@bonzini bonzini removed this from the 1.10 milestone Nov 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants