[OE-core] [PATCH] gobject-introspection: relocate typelib repository for native builds

Sascha Silbe x-yo17 at se-silbe.de
Fri Jun 8 18:17:37 UTC 2018


Alexander Kanavin <alex.kanavin at gmail.com> writes:

> 2018-06-08 19:18 GMT+03:00 Sascha Silbe <x-yo17 at 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

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: python3-pygobject-test_1.0.bb
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20180608/853c6736/attachment-0002.ksh>
-------------- next part --------------

-- 
Softwareentwicklung Sascha Silbe, Niederhofenstra?e 5/1, 71229 Leonberg
https://se-silbe.de/
USt-IdNr.: DE281696641
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20180608/853c6736/attachment-0002.sig>


More information about the Openembedded-core mailing list