From: "Daniel P. Berrangé" <berrange@redhat.com>
To: marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"John Snow" <jsnow@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH 0/4] Add meson wrap fallback for slirp & dtc
Date: Mon, 6 Mar 2023 10:06:05 +0000 [thread overview]
Message-ID: <ZAW7DcpRDcGF2VQx@redhat.com> (raw)
In-Reply-To: <20230302131848.1527460-1-marcandre.lureau@redhat.com>
On Thu, Mar 02, 2023 at 05:18:44PM +0400, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Hi,
>
> Meson "wrap" is a mechanism to build dependencies that doesn't rely on git
> submodules and integrate external dependencies as subproject()s.
>
> This offers developpers a simpler way to build QEMU with missing system
> dependencies (ex, libslirp in my case), but also simplify the fallback build
> definition of dtc/libfdt.
Do we actually need this facility though ? We've already determined
that every platform we need has libslirp now, and IIUC Thomas determined
recently that dtc is also available everywhere we need it to be.
So why would we want to continue to special case these two libraries,
out of all the many many many other libraries we also have deps on.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-03-06 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 13:18 [PATCH 0/4] Add meson wrap fallback for slirp & dtc marcandre.lureau
2023-03-02 13:18 ` [PATCH 1/4] mtest2make.py: teach suite name that are just "PROJECT" marcandre.lureau
2023-03-02 13:18 ` [PATCH 2/4] build-sys: prevent meson from downloading wrapped subprojects marcandre.lureau
2023-03-02 13:18 ` [PATCH 3/4] build-sys: add slirp.wrap marcandre.lureau
2023-03-02 13:18 ` [PATCH 4/4] build-sys: replace dtc submodule with dtc.wrap marcandre.lureau
2023-03-06 10:06 ` Daniel P. Berrangé [this message]
2023-03-06 10:17 ` [PATCH 0/4] Add meson wrap fallback for slirp & dtc Peter Maydell
2023-03-06 10:25 ` Marc-André Lureau
2023-03-06 10:19 ` Marc-André Lureau
2023-03-06 10:32 ` Daniel P. Berrangé
2023-03-06 10:41 ` Marc-André Lureau
2023-03-06 11:36 ` Paolo Bonzini
2023-03-07 11:19 ` Daniel P. Berrangé
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=ZAW7DcpRDcGF2VQx@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).