From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkgconf: Add a symlink to the GNU_TARGET_NAME-pkg-config
Date: Tue, 1 Mar 2016 22:12:45 +0100 [thread overview]
Message-ID: <56D605CD.1070008@mind.be> (raw)
In-Reply-To: <20160229213520.2b6e6ee7@free-electrons.com>
On 02/29/16 21:35, Thomas Petazzoni wrote:
[snip]
> 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.
For exactly this reason I would like to introduce a config-script directory,
e.g. $(HOST_DIR)/usr/cross-bin. In this directory we would put the
cross-pkg-config and the fixed up config scripts we now search for in
$(STAGING_DIR)/usr/bin.
Regards,
Arnout
>
> However, doing this change means that any configure script or Makefile
> that calls pkg-config directly would no longer find our pkg-config.
>
> Best regards,
>
> Thomas
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-03-01 21:12 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
2016-03-01 8:15 ` Peter Korsgaard
2016-03-01 21:12 ` Arnout Vandecappelle [this message]
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=56D605CD.1070008@mind.be \
--to=arnout@mind.be \
--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