From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] package/meson: use specific BR variables for cross-compilation.conf
Date: Tue, 15 Sep 2020 22:50:36 +0200 [thread overview]
Message-ID: <20200915225036.7e858a1e@windsurf.hq.k.grp> (raw)
In-Reply-To: <CADYdroOFr0KdVKspvj28ERrFShHv28zHzsmQuwo7EPhm9NsdxQ@mail.gmail.com>
On Tue, 15 Sep 2020 17:46:18 +0200
Norbert Lange <nolange79@gmail.com> wrote:
> > This changes host/bin/pkgconf to host/bin/pkg-config, but that shouldn't
> > be a problem, given meson only uses this pkgconfig to find target
> > packages and not host packages (for that meson would look it up in a
> > native-file instead of a cross-file).
>
> Well, its used by all other build systems, so this makes more sense to me,
> otherwise, shouldn't PKG_CONFIG_HOST_BINARY be changed to pkgconfig?
No, for Meson things are special, and it should really point to pkgconf
directly, and not to Buildroot's pkg-config wrapper around pkgconf.
Otherwise, what you're doing essentially reverts
4e0bc29993376613d200e892d491e31ea5a49622.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-09-15 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 10:05 [Buildroot] [PATCH v2 1/3] package/pkg-meson.mk: fix generation of pkg_config_static prop Norbert Lange
2020-09-15 10:05 ` [Buildroot] [PATCH v2 2/3] package/meson: use specific BR variables for cross-compilation.conf Norbert Lange
2020-09-15 14:05 ` Nicolas Cavallari
2020-09-15 15:46 ` Norbert Lange
2020-09-15 20:50 ` Thomas Petazzoni [this message]
2020-09-16 7:42 ` Nicolas Cavallari
2020-09-15 10:05 ` [Buildroot] [PATCH v2 3/3] package/pkg-meson: move crosscompilation support out of package Norbert Lange
2020-09-15 10:24 ` Norbert Lange
2020-09-15 21:27 ` [Buildroot] [PATCH v2 1/3] package/pkg-meson.mk: fix generation of pkg_config_static prop Peter Seiderer
2020-09-16 16:34 ` Peter Seiderer
2020-09-27 7:34 ` Yann E. MORIN
2020-10-02 8:48 ` Peter Korsgaard
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=20200915225036.7e858a1e@windsurf.hq.k.grp \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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