All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: = ? UTF-8 ? B ? Ww== ? =oe= ? UTF-8 ? B ? XQ== ? = How to sane replace a path in a pkgconfig file ?
Date: Mon, 15 Feb 2010 09:44:21 +0000	[thread overview]
Message-ID: <1266227061.6436.3.camel@rex> (raw)
In-Reply-To: <1266182728.5437.31.camel@lenovo.internal.reciva.com>

On Sun, 2010-02-14 at 21:25 +0000, Phil Blundell wrote:
> On Sun, 2010-02-14 at 21:38 +0100, bernhard.guillon@opensimpad.org
> wrote:
> >  for i in `find ${S}/ -name "*.pc" -type f` ; do 
> > -            sed -i -e 's:-L${STAGING_LIBDIR}::g' -e 's:-I${STAGING_INCDIR}::g' $i
> > +            sed -i -e 's:-L${STAGING_LIBDIR}::g' -e 's:-I${STAGING_INCDIR}::g' -e 's:-rpath-link,${STAGING_LIBDIR}::g' $i
> >          done
> 
> That probably is a reasonable thing to do, but you might want to filter
> out the preceding "-Wl," as well.

Note its pkgconfig we're talking about here which should never be
putting this stuff in its .pc files in the first place as it has some
understanding of sysroots. Usually if these things are creeping in, its
due to dependencies being added as via its expanded cflags/libs lines
rather than as a true dependency.

I'm not sure how it copes with --rpath-link though. If that is breaking,
we should consider fixing pkgconfig itself.

Cheers,

Richard




      reply	other threads:[~2010-02-15  9:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 14:23 How to sane replace a path in a pkgconfig file ? bernhard.guillon
2010-02-14 17:04 ` Bernhard Reutner-Fischer
2010-02-14 17:33   ` = ? UTF-8 ? B ? Ww== ? =oe= ? UTF-8 ? B ? XQ== ? = " bernhard.guillon
2010-02-14 18:37     ` Bernhard Reutner-Fischer
2010-02-14 20:20       ` Koen Kooi
2010-02-14 20:38         ` bernhard.guillon
2010-02-14 21:22           ` Bernhard Reutner-Fischer
2010-02-14 21:31             ` Phil Blundell
2010-02-14 21:47               ` Bernhard Reutner-Fischer
2010-02-14 21:49                 ` Bernhard Reutner-Fischer
2010-02-14 21:25           ` Phil Blundell
2010-02-15  9:44             ` Richard Purdie [this message]

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=1266227061.6436.3.camel@rex \
    --to=rpurdie@rpsys.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.