| Summary: | glib-2.0 doesn't run gio-querymodules | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | core | Assignee: | Jussi Kukkonen <jku> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher |
| Version: | 2.0 | ||
| Target Milestone: | 2.1 M4 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2016-03-11 14:06:18 UTC
Documenting progress so far:
the resulting cache file is arch-independent but gio-querymodules actually loads the module in question (to query the extension point name). So doing this in natively in sysroot is probably not an option as all the module dependencies need to be built. So the postinstall for rootfs case could be something like:
qemuwrapper -L ${D} ${D}${bindir}/gio-querymodules ${D}${libdir}/gio/modules/
Ross: There's 3 recipes in oe-core that need these postinst/rm scripts. should I use postinst_intercept for this? (My guess was that that is what's used to run a postinst only once during rootfs creation but I could be wrong...)
This is fixed since poky commit cef8bc9e80c.
Verifying this would include checking that
* ${libexecdir}/gio-querymodules is on image
* ${libdir}/gio/modules/giomodule.cache has been created
Should be done on Sato image (or something that has glib-networking or gconf on it).
|