From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alexander.kanavin@linux.intel.com>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
	by mail.openembedded.org (Postfix) with ESMTP id 35E8176B7C
	for <openembedded-core@lists.openembedded.org>;
	Wed, 11 Nov 2015 13:47:19 +0000 (UTC)
Received: from orsmga003.jf.intel.com ([10.7.209.27])
	by fmsmga101.fm.intel.com with ESMTP; 11 Nov 2015 05:47:15 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.20,276,1444719600"; d="scan'208";a="682954015"
Received: from kanavin-desktop.fi.intel.com (HELO [10.237.68.161])
	([10.237.68.161])
	by orsmga003.jf.intel.com with ESMTP; 11 Nov 2015 05:47:14 -0800
Message-ID: <56434723.5090605@linux.intel.com>
Date: Wed, 11 Nov 2015 15:48:19 +0200
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Icedove/31.8.0
MIME-Version: 1.0
To: Mark Hatle <mark.hatle@windriver.com>, 
	openembedded-core@lists.openembedded.org
References: <cover.1447080392.git.alexander.kanavin@linux.intel.com>
	<5641FFD4.1050506@windriver.com> <56420F08.1050209@linux.intel.com>
	<56421DA6.5080700@windriver.com> <56433886.3060700@linux.intel.com>
	<564343E9.9020702@windriver.com>
In-Reply-To: <564343E9.9020702@windriver.com>
Subject: Re: [PATCH 00/29] Add gobject introspection support to oe-core
X-BeenThere: openembedded-core@lists.openembedded.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Patches and discussions about the oe-core layer
	<openembedded-core.lists.openembedded.org>
List-Unsubscribe: <http://lists.openembedded.org/mailman/options/openembedded-core>,
	<mailto:openembedded-core-request@lists.openembedded.org?subject=unsubscribe>
List-Archive: <http://lists.openembedded.org/pipermail/openembedded-core/>
List-Post: <mailto:openembedded-core@lists.openembedded.org>
List-Help: <mailto:openembedded-core-request@lists.openembedded.org?subject=help>
List-Subscribe: <http://lists.openembedded.org/mailman/listinfo/openembedded-core>,
	<mailto:openembedded-core-request@lists.openembedded.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2015 13:47:21 -0000
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 11/11/2015 03:34 PM, Mark Hatle wrote:

> Also has anyone looked at the .typelib information and determined if any of it
> is available via direct inspection via readelf, dwarf interpretation or other
> method that does not require execution?  Is there a definition of the .typelib
> information anywhere and some simple examples of how its generated by the
> runtime objects?  (To pursue this, the way forward is to determine a way to
> generate the .typelib by reading the chosen binaries in some way -- and then
> running a 'ptest' like check that the generated and runtime versions result in
> the same data.)

You can simply take a look at any of the .gir files: they are XMLs that 
are used to generate typelibs and contain essentially the same information.

I think it's totally unrealistic to extract all the high-level OOP 
semantics from .so libraries with readelf and friends.

For instance, gstreamer pipelines:


     <class name="Bin"
            c:symbol-prefix="bin"
            c:type="GstBin"
            parent="Element"
            glib:type-name="GstBin"
            glib:get-type="gst_bin_get_type"
            glib:type-struct="BinClass">
       <implements name="ChildProxy"/>
       <constructor name="new" c:identifier="gst_bin_new">
         <return-value transfer-ownership="none">
           <type name="Element" c:type="GstElement*"/>
         </return-value>
         <parameters>
           <parameter name="name"
                      transfer-ownership="none"
                      nullable="1"
                      allow-none="1">
             <doc xml:space="preserve">the name of the new bin</doc>
             <type name="utf8" c:type="const gchar*"/>
           </parameter>
         </parameters>
       </constructor>
       <virtual-method name="add_element">
         <return-value transfer-ownership="none">
           <type name="gboolean" c:type="gboolean"/>
         </return-value>
         <parameters>
...

etc etc etc.


Alex