Re: [PATCH 00/29] Add gobject introspection support to oe-core

[Alexander Kanavin <alexander.kanavin@linux.intel.com>]

On 11/10/2015 06:39 PM, Mark Hatle wrote:

>> This requires custom bitbake support I'm afraid, a specialist needs to
>> answer this.
>>
>
> Let me rephrase.  Instead of calling out to qemu (or a real target) for a
> gobject and result.  Can the result be cached (like we do with the config-site
> info?)  This would allow me to run say a MIPS64 n64 gobject build, cache the
> results and use it on my octeon3 build (which can't run in QEMU.)

The results in this case are .typelib files. They are raw dumps of a C 
structure in memory - different compilers may produce different binary 
representations of those. I wouldn't trust that they are the same and 
that it's okay to copy them around like this. What makes you confident 
that they are?


Alex