From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] meson: fix botched compile check conversions
Date: Tue, 16 Nov 2021 13:15:12 +0000 [thread overview]
Message-ID: <YZOu4IQOf6nTtoZq@redhat.com> (raw)
In-Reply-To: <CAFEAcA_PKATU93e2UuoiJB2xbt_y5WKtYY_D5t+SaozcDKQcyg@mail.gmail.com>
On Tue, Nov 16, 2021 at 01:10:04PM +0000, Peter Maydell wrote:
> On Tue, 16 Nov 2021 at 12:00, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > I wonder if the problem is more fundamental than that. Passing
> > stuff in --extra-cflags is done to influence the flags used to
> > compile the QEMU end user binaries. Unfortunately --extra-cflags
> > is also getting applied to all the meson.build feature checks.
> >
> > IMHO we would get a more reliable result if the meson.build
> > checks were fully isolated from the cflags we used for building
> > everything else, so the checks get a well understood, predictable
> > environment.
>
> If you're using --extra-cflags to pass in "-I/path/to/libfoo/headers"
> then you do want that to be used in the meson check for "do we have
> libfoo", though...
For pkg-config-ized things meson lets you override those paths
per-library IIRC.
For the non-pkg-config-izied case, that could be an argument for
specialized --extra-header-dir=PATH and --extra-lib-dir=$PATH args.
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:[~2021-11-16 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 9:38 [PATCH] meson: fix botched compile check conversions Paolo Bonzini
2021-11-16 11:13 ` Daniel P. Berrangé
2021-11-16 14:24 ` Paolo Bonzini
2021-11-16 11:51 ` Peter Maydell
2021-11-16 12:00 ` Daniel P. Berrangé
2021-11-16 13:10 ` Peter Maydell
2021-11-16 13:15 ` Daniel P. Berrangé [this message]
2021-11-16 14:31 ` Paolo Bonzini
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=YZOu4IQOf6nTtoZq@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@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 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.