Alexander Kanavin <alex.kana...@gmail.com> writes: > 2018-06-08 19:18 GMT+03:00 Sascha Silbe <x-y...@se-silbe.de>: >> gobject-introspection hard-codes the install path in the search path >> for the typelib repository, pretty much the same way glib behaves for >> the gio modules directory. Like for glib, this causes problems when >> gobject-introspection-native is restored from sstate with a different >> build directory. > > Can you provide an example of how the problems can be reproduced > please? I think we disable building introspection data for -native, > and so where typelib dir is shouldn't matter?
I originally encountered this issue in a poky-based project of one of my customers and used the recipe below to reproduce the issue in current poky master. To reproduce you can run: mkdir -p poky-downloads ( source poky/oe-init-build-env poky-move-test-1 && ln -s ../poky-downloads downloads && bitbake python3-pygobject-test && bitbake -c cleansstate python3-pygobject-test ) && rm -rf poky-move-test-1/tmp && ( source poky/oe-init-build-env poky-move-test-2 && ln -s ../poky-downloads downloads && ln -s ../poky-move-test-1/sstate-cache . && bitbake python3-pygobject-test ) Sascha
SUMMARY = "Python GObject bindings test"
SECTION = "devel/python"
LICENSE = "CLOSED"
DEPENDS = "glib-2.0-native python3-native python3-pygobject-native"
inherit python3native
do_compile() {
python3 -c 'from gi.repository import GLib'
}
BBCLASSEXTEND = "native"
-- Softwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg https://se-silbe.de/ USt-IdNr.: DE281696641
signature.asc
Description: PGP signature
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
