From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NuDTe-0005ey-3i
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 19:25:38 -0400
Received: from [140.186.70.92] (port=46281 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NuDTb-0005d0-Ue
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 19:25:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1NuDTZ-0003cB-99
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 19:25:35 -0400
Received: from mail2.shareable.org ([80.68.89.115]:50815)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1NuDTZ-0003c6-4m
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 19:25:33 -0400
Date: Tue, 23 Mar 2010 23:25:31 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in
	libvirt
Message-ID: <20100323232531.GE20130@shareable.org>
References: <4BA7C40C.2040505@codemonkey.ws>
	<20100322201003.GC28709@redhat.com>
	<4BA7E5E1.1010404@codemonkey.ws>
	<BACDE2EB-718C-41C9-9ED3-F3AB178DE6BF@suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BACDE2EB-718C-41C9-9ED3-F3AB178DE6BF@suse.de>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>, qemu-devel <qemu-devel@nongnu.org>

Alexander Graf wrote:
> I don't see why we shouldn't be able to automatically generate
> libqemu.so. We have the *.hx files that describe the syntax of
> parameters plus list all available options / commands. I'm not sure
> how exactly QMP works, but having a generic QMP command to list all
> available options would be handy too.
> 
> By then we could automate most of the library, making the glueing
> really easy. If libvirt doesn't properly link against libqemu anymore
> we also know why: The ABI changed.

I'm thinking most potential uses of the binary API, other than C
programmers, would be happier with a D-Bus version generated from
those same *.hx files.  Because then it's easy to call the API from
Python, Perl, even shell, etc.  Whereas libqemu.so would be relatively
difficult to use from those languages.

(Aside: I don't particularly like D-Bus.  But it does seem to work
for this sort of thing.)

-- Jamie