From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: pkgconfig.bbclass changes
Date: Tue, 23 Sep 2008 13:52:02 -0400 [thread overview]
Message-ID: <48D92CC2.7010300@balister.org> (raw)
In-Reply-To: <20080923122259.GA32730@mi.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
Henning Heinold wrote:
> On Tue, Sep 23, 2008 at 01:54:23PM +0200, Koen Kooi wrote:
>> Hi,
>>
>> Henning fixed up pkgconfig.bbclass (which should die, since
>> autotools.bbclass does a much better job), but I think this:
>>
>> - for pc in `find ${S} -name '*.pc' -type f | grep -v --
>> '-uninstalled.pc$'`; do
>> + for pc in `find ${D} -name '*.pc' -type f | grep -v --
>> '-uninstalled.pc$'`; do
>>
>> breaks -native recipes.
>>
>> regards,
>>
>> Koen
>
> Hi,
>
> sorry you are right. This indeed breaks native packages I didnt
> thought of it, while fixing the pc file of xine.
Does anyone know what the proper fix is? .dev does not build at the moment.
Philip
> I think we can not let die pkgconfig.bbclass, because not all features are
> in autotools.class and there are cases where staging or install
> do not depend on the autotools install routines.
>
> Bye Henning
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-09-23 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 11:54 pkgconfig.bbclass changes Koen Kooi
2008-09-23 12:22 ` Henning Heinold
2008-09-23 13:38 ` Koen Kooi
2008-09-23 17:52 ` Philip Balister [this message]
2008-09-23 18:21 ` Koen Kooi
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=48D92CC2.7010300@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
/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