From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Liviu Ionescu" <ilg@livius.net>,
"G 3" <programmingkidx@gmail.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [RFC] QEMU as Xcode project on macOS
Date: Fri, 11 Sep 2020 19:33:28 +0200 [thread overview]
Message-ID: <2921188.XSTMq4hUFX@silver> (raw)
In-Reply-To: <0b0b02e9-7925-b112-4056-c17e067a5278@redhat.com>
On Freitag, 11. September 2020 19:19:05 CEST Paolo Bonzini wrote:
> On 10/09/20 16:40, Christian Schoenebeck wrote:
> > If it turns out to work fine, then maybe I just push a branch of QEMU for
> > Mac developers somewhere for a while, as I think it would lower the entry
> > level for new developers on Mac tremendously. Apparently there is still
> > more changes with Meson ahead anyway (getting rid of the Makefiles or
> > whatever else is planned). So we'll see ...
>
> If there are no submodule dependencies (capstone/libfdt/slirp),
> effectively you can already behave as if the Makefiles did not exist and
> build QEMU with ninja and "meson test". So you could build your scripts
> from there.
>
> Paolo
Good to know, thanks!
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2020-09-11 17:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 12:56 [RFC] QEMU as Xcode project on macOS Christian Schoenebeck
2020-09-09 13:30 ` 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 [this message]
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=2921188.XSTMq4hUFX@silver \
--to=qemu_oss@crudebyte.com \
--cc=berrange@redhat.com \
--cc=ilg@livius.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.