From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
Date: Sat, 8 Jul 2006 11:13:52 -0400 [thread overview]
Message-ID: <20060708151352.GA868@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <44AFC907.3080704@gmail.com>
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.
next prev parent reply other threads:[~2006-07-08 15:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 18:11 [Qemu-devel] QEMU GUI Fabrice Bellard
2006-06-21 19:42 ` Mike Kronenberg
2006-06-22 19:32 ` gbeauchesne
2006-06-22 19:32 ` gbeauchesne
2006-06-28 23:03 ` Joe Lee
2006-06-29 13:19 ` Daniel P. Berrange
2006-06-29 21:05 ` Joe Lee
2006-06-29 21:47 ` Daniel P. Berrange
2006-06-22 15:06 ` Luca Barbato
2006-07-01 22:47 ` Chris Wilson
2006-07-05 20:51 ` Luca Barbato
2006-07-08 2:14 ` Chris Wilson
2006-07-08 2:46 ` Johannes Schindelin
2006-07-08 6:34 ` M. Warner Losh
2006-07-08 14:34 ` wxWidgets and C: was " Jim C. Brown
2006-07-08 15:02 ` Joe Lee
2006-07-08 15:13 ` Jim C. Brown [this message]
2006-07-08 16:34 ` Kevin F. Quinn
2006-07-08 21:26 ` Oliver Gerlich
2006-07-10 0:03 ` John R.
2006-07-10 0:10 ` Jim C. Brown
2006-07-11 7:44 ` David Fraser
2006-07-11 12:40 ` Jason Gress
2006-07-11 13:17 ` Linas Žvirblis
2006-07-11 14:52 ` Oliver Gerlich
2006-07-11 15:29 ` Linas Žvirblis
2006-07-12 8:17 ` Luca Barbato
2006-07-12 13:15 ` [Qemu-devel] Insert module into kernel Tieu Ma Dau
2006-07-12 13:36 ` Paul Brook
2006-07-13 8:11 ` Tieu Ma Dau
2006-06-22 15:18 ` [Qemu-devel] QEMU GUI Christian MICHON
2006-06-30 10:28 ` Dan Sandberg
2006-06-22 21:50 ` Anthony Liguori
2006-06-23 0:18 ` Kevin F. Quinn
2006-06-23 1:53 ` Anthony Liguori
2006-06-23 7:17 ` Kevin F. Quinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060708151352.GA868@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).