From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FzEVK-0003bb-69 for qemu-devel@nongnu.org; Sat, 08 Jul 2006 11:13:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FzEVJ-0003b8-BL for qemu-devel@nongnu.org; Sat, 08 Jul 2006 11:13:57 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FzEVJ-0003b5-5u for qemu-devel@nongnu.org; Sat, 08 Jul 2006 11:13:57 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FzEVy-0003w4-BM for qemu-devel@nongnu.org; Sat, 08 Jul 2006 11:14:38 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.250.193]) by po1.wam.umd.edu (8.12.11.20060308/8.12.11) with ESMTP id k68FDsfM003407 for ; Sat, 8 Jul 2006 11:13:54 -0400 (EDT) Date: Sat, 8 Jul 2006 11:13:52 -0400 From: "Jim C. Brown" Subject: Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI Message-ID: <20060708151352.GA868@jbrown.mylinuxbox.org> References: <44AC2667.8030008@gentoo.org> <20060708.003444.-399284312.imp@bsdimp.com> <20060708143413.GA20596@jbrown.mylinuxbox.org> <44AFC907.3080704@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44AFC907.3080704@gmail.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Sat, Jul 08, 2006 at 11:02:31AM -0400, Joe Lee wrote: > Jim C. Brown wrote: > >For the record, we can use wxWidgets in qemu even though we can not use C++ > >in qemu (something that I would be strongly against). > > > >http://wxc.sourceforge.net/ > > > >Requiring this as a dependency would make it easier to deal with issues > >such as > >C++ ABI compatibility by avoiding the direct use of C++. > > > >There's a QtC that I considered using for a Qt GUI for qemu. > > > > > How about WX using Python - Is that an option? > -joe > Good question. I'm not aware of a way to call Python code from inside of C. I suppose if we could compile it into a shared library of some sort, that would do the trick. (I'm assuming the Python lib would compile into something that was callable externally using the C ABI, not the C++ ABI. If it's the latter then using Python would still be a bad idea.) I'm of the opinion that it would just be easier to use wxc directly instead of trying to use a Python binding in a C project, though. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.