Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
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: Sun, 14 Feb 2010 22:47:09 +0100	[thread overview]
Message-ID: <20100214214709.GJ30265@mx.loc> (raw)
In-Reply-To: <1266183110.5437.34.camel@lenovo.internal.reciva.com>

On Sun, Feb 14, 2010 at 09:31:50PM +0000, Phil Blundell wrote:
>On Sun, 2010-02-14 at 22:22 +0100, Bernhard Reutner-Fischer wrote:
>> I'd go for plain
>> sed -i -e 's:${STAGING_LIBDIR}::g' -e 's:${STAGING_INCDIR}::g' $i
>> 
>> to avoid massaging  -rpath / -Y / --library-path et al later on.
>
>Does that actually work?  I would have thought it would leave you with a
>load of surplus "-L" and "-I" options with missing arguments.

It wouldn't, you're right.
So either come up with a stanza that lists all path-touching tokens
explicitly or write a sed/awk script that does that -- i'd be surprised
if nobody wrote something like that yet since that's a pretty common
thing to do.



  reply	other threads:[~2010-02-14 21:46 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 [this message]
2010-02-14 21:49                 ` Bernhard Reutner-Fischer
2010-02-14 21:25           ` Phil Blundell
2010-02-15  9:44             ` Richard Purdie

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=20100214214709.GJ30265@mx.loc \
    --to=rep.dot.nop@gmail.com \
    --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