On 11/17/2015 05:02 PM, Mark Hatle wrote:
So the bottom line, to generate introspection info, you have to run the
code of the library that you introspect, either with QEMU, or on target
hardware, and I don't see a way to avoid this, short of complete rewrite
of the entire glib ecosystem. If someone wants to have this feature, but
doesn't have a working QEMU, they should get their act together and fix it.
Can you put together a small piece of test code with instructions on how to
compiler it, generate the '.gir' file and anything else? I can take a look at
this and see if there is a way to inspect the intermediate objects for the type
information we need.
Alright. Here you go:
https://github.com/kanavin/gi-library-boilerplate
In there you have a library that provides:
1) A simple class called MamanBar that is final (i.e. cannot be derived
from) and has one public method and some internal state.
2) An interface called MamanIbaz which specified two methods and one
property.
3) A derivable (can be subclassed) class called MamanBaz which
implements the above interface, and also adds a virtual method and a signal.
When you run 'make', you'll get both the library and the introspection
data - .gir and .typelib files.
All of the above is written using best current knowledge from the
GObject manual:
https://developer.gnome.org/gobject/stable/index.html
Regards,
Alex
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
