From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/3] meson: Don't pass 'method' to dependency()
Date: Wed, 19 Jan 2022 17:38:38 +0000 [thread overview]
Message-ID: <YehMnmZp3z+Cr0Od@redhat.com> (raw)
In-Reply-To: <20220119171800.491703-1-abologna@redhat.com>
On Wed, Jan 19, 2022 at 06:17:57PM +0100, Andrea Bolognani wrote:
> See [1] for recent discussion about libgcrypt specifically, which the
> first patch is about.
>
> After writing that one, I realized that there is no point in
> explicitly passing 'method' to dependency() because Meson will do the
> right thing by default - hence the next two patches.
This whole series is effectively reverting
commit 1a94933fcc3d641bda9988244cde61769baae2e5
Author: Paolo Bonzini <pbonzini@redhat.com>
Date: Mon Aug 31 06:27:00 2020 -0400
meson: use pkg-config method to find dependencies
We do not need to ask cmake for the dependencies, so just use the
pkg-config mechanism. Keep "auto" for SDL so that it tries using
sdl-config too.
The documentation is adjusted to use SDL2_image as the example,
rather than SDL which does not use the "pkg-config" method.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
which IIRC was done to get rid of mesons' confusing/misleading
attempts to probe for things via cmake when the pkg-config file
is not present.
>
> [1] https://lists.gnu.org/archive/html/qemu-devel/2022-01/msg01224.html
>
> Andrea Bolognani (3):
> meson: Don't force use of libgcrypt-config
> meson: Don't pass 'method' to dependency()
> docs: Don't recommend passing 'method' to dependency()
>
> docs/devel/build-system.rst | 1 -
> meson.build | 75 +++++++++++++++----------------------
> tcg/meson.build | 2 +-
> 3 files changed, 31 insertions(+), 47 deletions(-)
>
> --
> 2.34.1
>
>
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:[~2022-01-19 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 17:17 [PATCH 0/3] meson: Don't pass 'method' to dependency() Andrea Bolognani
2022-01-19 17:17 ` [PATCH 1/3] meson: Don't force use of libgcrypt-config Andrea Bolognani
2022-01-19 17:17 ` [PATCH 2/3] meson: Don't pass 'method' to dependency() Andrea Bolognani
2022-01-19 17:18 ` [PATCH 3/3] docs: Don't recommend passing " Andrea Bolognani
2022-01-19 17:38 ` Daniel P. Berrangé [this message]
2022-01-19 17:45 ` [PATCH 0/3] meson: Don't pass " Andrea Bolognani
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=YehMnmZp3z+Cr0Od@redhat.com \
--to=berrange@redhat.com \
--cc=abologna@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).