From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/3] gst-ffmpeg: add --pkg-config to internal libav configure options
Date: Sat, 18 Oct 2014 13:51:02 +0200 [thread overview]
Message-ID: <20141018135102.4b4d86df@free-electrons.com> (raw)
In-Reply-To: <20141017212453.GI3971@free.fr>
Dear Yann E. MORIN,
On Fri, 17 Oct 2014 23:24:53 +0200, Yann E. MORIN wrote:
> > WARNING: .../output/host/usr/bin/i686-pc-linux-gnu-pkg-config not found, library detection may fail.
>
> Instead of fixing just that one package, shouldn't we provide a symlink:
> TUPLE-pkg-config -> pkg-config
>
> This way, all packages that expect a cross-pkg-config will work without
> customisation.
>
> Thomas, thoughts?
I don't have a very strong opinion here. How many packages expect
TUPLE-pkg-config instead of pkg-config? I'm not sure it's really the
majority, and if it's not, I prefer to keep handling this on a
per-package basis rather than adding a symlink.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-18 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 19:30 [Buildroot] [PATCH v3 1/3] gst-ffmpeg: add option to select GPL vs LGPL build Danomi Manchego
2014-10-12 19:30 ` [Buildroot] [PATCH v3 2/3] gst-ffmpeg: add --pkg-config to internal libav configure options Danomi Manchego
2014-10-13 13:37 ` Luca Ceresoli
2014-10-13 16:26 ` Danomi Manchego
2014-10-14 8:59 ` Luca Ceresoli
2014-10-17 21:24 ` Yann E. MORIN
2014-10-17 21:39 ` Bernd Kuhls
2014-10-17 22:46 ` Yann E. MORIN
2014-10-18 11:51 ` Thomas Petazzoni [this message]
2014-10-18 13:14 ` Arnout Vandecappelle
2014-10-12 19:30 ` [Buildroot] [PATCH v3 3/3] gst-ffmpeg: expand package description to describe libav usage Danomi Manchego
2014-10-13 12:15 ` Luca Ceresoli
2014-10-13 12:16 ` [Buildroot] [PATCH v3 1/3] gst-ffmpeg: add option to select GPL vs LGPL build Luca Ceresoli
2014-10-17 21:32 ` 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=20141018135102.4b4d86df@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