From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <rth@twiddle.net>,
Paolo Bonzini <pbonzini@redhat.com>,
programmingkidx@gmail.com, Gerd Hoffmann <kraxel@redhat.com>,
Thomas Huth <thuth@redhat.com>
Subject: [RFC] QEMU as Xcode project on macOS
Date: Wed, 09 Sep 2020 14:56:46 +0200 [thread overview]
Message-ID: <2764135.D4k31Gy3CM@silver> (raw)
I've recently been thinking about how feasible a stripped down Xcode project
for QEMU would be, i.e. you just get the QEMU sources, click on
qemu.xcodeproj, Cmd + B, done. No extra installation, no configure, nothing.
I've done this before for gtk(mm), which you might know, depends on approx. 24
individual libraries (glib, jpeg, png, pixman, atk, gdk, cairo, pixman,
graphene, sigcpp, ... gtk, gtkmm) that you would usually all need to download
and
./configure && make & make install
each individually on macOS. Or right, you could alternatively "just install"
them from Homebrew, MacPorts, Fink. But no matter which solution you choose,
it easily ends up in a mess (conflicts, misbehaviours) on macOS to install
libs and apps globally. And I think that's the problem why there are currently
relatively little contribution for QEMU coming from devs on macOS. Because you
don't want to install things globally on a macOS system, it's simply not
working well there as it does with Linux distros.
And the other thing is: I've tested the waters with Apple and filed a QEMU
related macOS bug with them. The response was like expected; they basically
said 'if there's no Xcode project, then we don't investigate it'.
The question is, and I don't have the big picture of QEMU yet to judge that,
how much is auto generated for QEMU i.e. with custom scripts that would
probably destroy this plan? There are these trace calls that are auto
generated, is there more like the TCG part for instance?
What I could imagine: a hand crafted Xcode project as a starting point, and if
that works out, switching to auto generating that Xcode project from the Meson
inftrastructure to avoid multiplication of maintenance effort.
Best regards,
Christian Schoenebeck
next reply other threads:[~2020-09-09 12:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 12:56 Christian Schoenebeck [this message]
2020-09-09 13:30 ` [RFC] QEMU as Xcode project on macOS Peter Maydell
2020-09-09 13:43 ` Liviu Ionescu
2020-09-09 17:32 ` Christian Schoenebeck
2020-09-09 17:45 ` Liviu Ionescu
2020-09-09 18:13 ` Daniel P. Berrangé
2020-09-09 18:56 ` Christian Schoenebeck
2020-09-09 19:03 ` Liviu Ionescu
2020-09-09 19:26 ` Christian Schoenebeck
2020-09-09 19:16 ` Peter Maydell
2020-09-09 20:13 ` Liviu Ionescu
2020-09-10 9:20 ` Paolo Bonzini
2020-09-10 10:21 ` Liviu Ionescu
2020-09-10 7:37 ` Daniel P. Berrangé
2020-09-10 9:32 ` Christian Schoenebeck
2020-09-10 9:39 ` Daniel P. Berrangé
2020-09-10 10:14 ` Christian Schoenebeck
2020-09-10 10:24 ` Liviu Ionescu
2020-09-10 10:35 ` Peter Maydell
2020-09-10 10:45 ` Daniel P. Berrangé
2020-09-10 10:56 ` Liviu Ionescu
2020-09-10 14:40 ` Christian Schoenebeck
2020-09-11 17:19 ` Paolo Bonzini
2020-09-11 17:33 ` Christian Schoenebeck
2020-09-10 10:41 ` Paolo Bonzini
2020-09-10 10:54 ` Daniel P. Berrangé
2020-09-09 13:40 ` Daniel P. Berrangé
2020-09-09 13:41 ` Thomas Huth
2020-09-09 13:44 ` Daniel P. Berrangé
2020-09-09 15:16 ` Paolo Bonzini
2020-09-09 14:40 ` Programmingkid
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=2764135.D4k31Gy3CM@silver \
--to=qemu_oss@crudebyte.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/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).