From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] pkg-infra: add <pkg>_CONFIG_FIXUP to fix *-config files
Date: Fri, 18 Jan 2013 19:52:13 +0200 [thread overview]
Message-ID: <50F98BCD.90009@petroprogram.com> (raw)
In-Reply-To: <50F96F98.3010704@mind.be>
18.1.2013 17:51, Arnout Vandecappelle kirjoitti:
> On 18/01/13 13:58, Stefan Fr?berg wrote:
>> Hi Arnout!
>>
>> 17.1.2013 10:32, Arnout Vandecappelle kirjoitti:
> [snip]
>>> A generic solution could be the following: put a script in
>>> $(HOST_DIR)/usr/bin (or some other directory) that hands the known
>>> arguments to pkg-config and redirects the rest back to the original
>>> *-config script. This makes patching of the *-config script
>>> unnecessary in most cases.
>>>
>>
>> Sounds good but what about that<pkg>_CONFIG_FIXUP variable that was
>> started from Gustavo suggestion (originally from divine-config: fixup
>> thread) ?
>>
>> http://lists.busybox.net/pipermail/buildroot/2013-January/064656.html
>>
>> Was it now totally waste of time ? :-(
>
> Not at all. First of all, it got the discussion going which may
> eventually lead to an acceptable solution. Second, the generic
> solution is probably not implementable in the short term. Your patch
> certainly is, because it only refactors already-existing fixups into
> common infrastructure.
>
> I therefore think that your patch should be committed. Will there
> still be a v3 or is this it?
>
Well, I think this is it.
>
>>> Something to discuss (again) at the BR developer days?
>>>
>>>
>>>> I noticed that some *-config files have just prefix (and maybe
>>>> exec_prefix) but not any includedir or libdir defined inside them
>>>> and just give -I/usr/include for --cflags and -L/usr/lib for --libs
>>>
>>> Even worse! Which one does that?
>>>
>>
>> Well, at least:
>>
>> giblib-config --cflags gives -I/usr/include
>> neon-config --cflags gives -I/usr/include
>>
>> But Im using older 2012.08 buildroot so maybe they are fixed now?
>
> D'oh, I did a quick check in my allpkgconfig:
>
> for i in staging/usr/bin/*-config; \
> do $i --cflags | grep -e '-I/usr' && echo " --- $i"; \
> done
>
> 24 of the 41 *-config scripts give the wrong cflags (26/40 for
> --libs) (roughly 10 scripts need some other argument than
> --libs/--cflags).
>
> So I'd say that your patch is sorely needed :-)
>
>
>
> Regards,
> Arnout
>
> [snip]
Nicely :-)
Stefan
next prev parent reply other threads:[~2013-01-18 17:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 19:52 [Buildroot] [PATCH v2] pkg-infra: add <pkg>_CONFIG_FIXUP to fix *-config files Stefan Fröberg
2013-01-10 19:52 ` Stefan Fröberg
2013-01-10 20:19 ` Thomas Petazzoni
2013-01-10 20:47 ` Yann E. MORIN
2013-01-10 21:15 ` Stefan Fröberg
2013-01-10 21:22 ` Yann E. MORIN
2013-01-10 21:01 ` Stefan Fröberg
2013-01-11 21:33 ` Arnout Vandecappelle
2013-01-12 1:38 ` Stefan Fröberg
2013-01-17 8:32 ` Arnout Vandecappelle
2013-01-18 12:58 ` Stefan Fröberg
2013-01-18 15:23 ` Thomas Petazzoni
2013-01-18 17:55 ` Stefan Fröberg
2013-01-18 15:51 ` Arnout Vandecappelle
2013-01-18 17:52 ` Stefan Fröberg [this message]
2013-01-20 11:36 ` Arnout Vandecappelle
2013-01-20 12:35 ` Samuel Martin
2013-01-20 14:37 ` Stefan Fröberg
2013-01-20 17:27 ` Arnout Vandecappelle
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=50F98BCD.90009@petroprogram.com \
--to=stefan.froberg@petroprogram.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