From: Samuel Thibault <samuel.thibault@gnu.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH slirp 0/5] Make it a standalone project
Date: Sun, 10 Feb 2019 22:38:39 +0100 [thread overview]
Message-ID: <20190210213839.vfocl3mv2ivgz5h2@function> (raw)
In-Reply-To: <CAFEAcA-P_vVy8dbti83Afm6CMNZBmr5FUzMeztCwp=NRXwn5qw@mail.gmail.com>
Hello,
Peter Maydell, le dim. 10 févr. 2019 21:35:37 +0000, a ecrit:
> On Fri, 8 Feb 2019 at 20:58, <marcandre.lureau@redhat.com> wrote:
> > As discussed earlier in "[PATCH for-3.2 00/41] RFC: slirp: make it
> > again a standalone project" and other threads, it would be useful to
> > make slirp a separate project (the submodule approach was discarded)
> > for various projects to share.
>
> > The following patches add meson build system (if necessary for older
> > distros, autotools could be added - however I believe python & ninja
> > are generally available on the QEMU supported platforms)
>
> Do you really need to make QEMU add an extra build dependency
> just to use a different build system?
AIUI, this patches series is meant for the slirp repository, not the
QEMU repository. I.e. just to show how it'll look like, until a project
it settled somewhere and the discussion can happen there.
Samuel
next prev parent reply other threads:[~2019-02-10 21:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 18:11 [Qemu-devel] [PATCH slirp 0/5] Make it a standalone project marcandre.lureau
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 1/5] Extract slirp/ from qemu repository marcandre.lureau
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 2/5] build-sys: add a meson build marcandre.lureau
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 3/5] build-sys: add version tooling marcandre.lureau
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 4/5] slirp: add state saving/loading marcandre.lureau
2019-02-09 11:40 ` Samuel Thibault
2019-02-09 13:09 ` Marc-André Lureau
2019-02-09 13:12 ` Samuel Thibault
2019-02-09 13:16 ` Marc-André Lureau
2019-02-09 13:19 ` Samuel Thibault
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 5/5] Add .gitlab-ci.yml marcandre.lureau
2019-02-09 11:33 ` [Qemu-devel] [PATCH slirp 0/5] Make it a standalone project Samuel Thibault
2019-02-10 21:35 ` Peter Maydell
2019-02-10 21:38 ` Samuel Thibault [this message]
2019-02-10 21:42 ` Peter Maydell
2019-02-10 22:03 ` Marc-André Lureau
2019-02-10 22:07 ` Peter Maydell
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=20190210213839.vfocl3mv2ivgz5h2@function \
--to=samuel.thibault@gnu.org \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--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).