Hi<div><br></div><div>Thanks for your suggestion. I also would like to support gir in oe-core. However, I need to cleanup the recipes now as you said. I will think about it because of my schedule :(.</div><div><br></div><div>I'll contact you when I'm ready for it.</div><div>Thanks<span></span><br><br>2015년 10월 6일 화요일, Alexander Kanavin<<a href="mailto:alexander.kanavin@linux.intel.com">alexander.kanavin@linux.intel.com</a>>님이 작성한 메시지:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I'm looking into the possibility of adding gobject introspection support directly to oe-core for Yocto 2.1 release (Spring 2016). This work would of course be based on meta-gir, but with the mandatory goal of producing patches of sufficient quality that can be sent upstream.<br>
<br>
I know the upstream tarball is a mess that mashes together several different things and was never designed for cross-compiling; and meta-gir is also difficult to understand: autotools-based build files are patched using undocumented patchfiles, then again patched from the recipe using sed, with no comments anywhere - all that needs to be sorted.<br>
<br>
What's your take on this? Is it realistic? Would you be able to help out?<br>
<br>
Regards,<br>
Alexander<br>
</blockquote></div>