package.bbclass: Allow overriding of debugedit starting path
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | package.bbclass: Allow overriding of debugedit starting pathmeta/ | +2 | 8 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] package.bbclass: Allow overriding of debugedit starting path
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(-)