From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] package.bbclass: Allow overriding of debugedit starting path
Date: Wed, 11 Jul 2012 11:00:38 -0500 [thread overview]
Message-ID: <cover.1342022120.git.peter.seebach@windriver.com> (raw)
We use a prebuilt toolchain which has all debug symbols start out
looking like
/opt/windriver/wrlinux/ia32/i686-wrs-linux-gnu/src/...
and we'd rather not start populating /opt on targets when we have all
this lovely logic for debug sources. This patch provides a generic
hook for overriding the starting path that debugedit will replace with
the canonical debugsrc path. This strikes me as a pretty low-impact
alternative to, say, encouraging such recipes to call debugedit
directly.
I am open to the idea of allowing a replacement to be specified,
too, but I didn't need that and don't immediately see why it'd matter.
And since I switch between scripting languages really often, and
this is a source of confusion: Yes, in Python, ("" or x) yields x.
The following changes since commit 20405bdab18b7a2b101f818e72863d289d5945e4:
Bruce Ashfield (1):
linux-yocto/3.0: perf scripting support
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/debugsrc
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/debugsrc
Peter Seebach (1):
package.bbclass: Allow overriding of debugedit starting path
meta/classes/package.bbclass | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
next reply other threads:[~2012-07-11 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 16:00 Peter Seebach [this message]
2012-07-11 16:00 ` [PATCH 1/1] package.bbclass: Allow overriding of debugedit starting path Peter Seebach
2012-07-11 16:12 ` Richard Purdie
2012-07-11 16:33 ` Peter Seebach
2012-07-11 17:36 ` Richard Purdie
2012-07-11 17:56 ` Ross Burton
2012-07-11 18:54 ` Peter Seebach
2012-07-11 19:01 ` Chris Larson
2012-07-11 19:54 ` Burton, Ross
2012-07-11 20:20 ` 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=cover.1342022120.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@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