Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkgconf: Add a symlink to the GNU_TARGET_NAME-pkg-config
Date: Tue, 1 Mar 2016 09:14:03 +0100	[thread overview]
Message-ID: <20160301091403.2b7ce2fc@free-electrons.com> (raw)
In-Reply-To: <87y4a3m7v5.fsf@dell.be.48ers.dk>

Peter,

On Tue, 01 Mar 2016 00:09:34 +0100, Peter Korsgaard wrote:

>  > What I dislike with the current setup is that if you add
>  > $(HOST_DIR)/usr/bin to your PATH, then any call to pkg-config returns
>  > values that are valid only when cross-compiling, which is not
>  > necessarily what one would expect.
> 
> On the other hand, the situations where you add it to the path are often
> where you _DO_ want to cross compile.

Indeed, but you often end up doing both cross-compilation and native
compilation, and it's pretty easy to get confused by a pkg-config
returning absurd values.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-03-01  8:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 18:22 [Buildroot] [PATCH] pkgconf: Add a symlink to the GNU_TARGET_NAME-pkg-config Jeroen Roovers
2016-02-29 19:19 ` Bernd Kuhls
2016-02-29 20:35   ` Thomas Petazzoni
2016-02-29 23:09     ` Peter Korsgaard
2016-03-01  8:14       ` Thomas Petazzoni [this message]
2016-03-01  8:15         ` Peter Korsgaard
2016-03-01 21:12     ` Arnout Vandecappelle
2016-03-18 17:24       ` Yann E. MORIN
2016-03-18 21:14         ` Arnout Vandecappelle
2016-03-02 20:25 ` Thomas Petazzoni
2016-03-18 17:25   ` Yann E. MORIN

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=20160301091403.2b7ce2fc@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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