Skip to content
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

Make GIR optional? #139

Closed
eternaleye opened this issue Sep 20, 2017 · 1 comment
Closed

Make GIR optional? #139

eternaleye opened this issue Sep 20, 2017 · 1 comment

Comments

@eternaleye
Copy link

Currently, the GObject Introspection support is hard-enabled. However, g-ir-scanner is rather painful for cross-compilation, and isn't needed for any of the things I need appstream for (Plasma Discover, in particular).

I tried brute-force hacking out the gir compilation from src/meson.build, and the result worked perfectly. Could this be put behind an option, which the vala option requires?

@ximion
Copy link
Owner

ximion commented Oct 1, 2017

Weird, my reply from weeks ago has vanished...
I wrote previously that I am usually against disabling such things, since it increases the amount of configurations to test and GIR is a very useful feature (and disabling it has a chance of language bindings getting out of sync).
However, cross-compilation is a good reason to want this functionality, and I know that GIR is pretty annoying in that particular scenario, especially if you just want to test something quickly.
So, I added an option to disable the generation of introspection data, and hope most people will never touch it ;-)

Cheers!

@ximion ximion closed this as completed in ccc0b2d Oct 1, 2017
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

No branches or pull requests

2 participants