From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Joshua Lock : packaged-staging: post-process non-binary files to fix paths packages
Date: Thu, 01 Apr 2010 17:34:25 +0100 [thread overview]
Message-ID: <1270139665.4993.152.camel@rex> (raw)
In-Reply-To: <1270137923.6277.101.camel@trini-m4400>
On Thu, 2010-04-01 at 09:05 -0700, Tom Rini wrote:
> On Thu, 2010-04-01 at 12:51 +0000, git version control wrote:
> > Module: openembedded.git
> > Branch: rpurdie/work-in-progress
> > Commit: 5df536641049c5af6413e410aa20bb97880fe897
> > URL: http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=5df536641049c5af6413e410aa20bb97880fe897
> >
> > Author: Joshua Lock <josh@linux.intel.com>
> > Date: Wed Mar 31 11:22:02 2010 +0100
> >
> > packaged-staging: post-process non-binary files to fix paths packages
> >
> > Add tooling from Poky to scan packages and fix up paths in libtool files, we
> > then build on this to further post-process native packages (native, cross, sdk)
> > and fix up any references to the STAGING_DIR in non-binary files.
> >
> > Signed-off-by: Joshua Lock <josh@linux.intel.com>
>
> There's a lot more than just .la files that get these paths wrong. If
> you use the scan_cmd you set on native/etc for everything you can fix
> them all up.
It scans everything for -native packages and just .la files for target
packages. I'd argue that for target packages we're better off fixing the
problems at source since the real target packages are probably also
bust?
Cheers,
Richard
next prev parent reply other threads:[~2010-04-01 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1NxJrs-0006SS-LZ@melo.openembedded.org>
2010-04-01 16:05 ` [oe-commits] Joshua Lock : packaged-staging: post-process non-binary files to fix paths packages Tom Rini
2010-04-01 16:34 ` Richard Purdie [this message]
2010-04-01 16:55 ` Tom Rini
2010-04-01 18:12 ` Richard Purdie
2010-04-01 19:49 ` Tom Rini
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=1270139665.4993.152.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.