On Wed, 2012-07-11 at 11:00 -0500, Peter Seebach wrote:
> In the usual case, the computed path used for debugedit to fix
> up path references for the target filesystem is correct. However,
> prebuilt binary components, such as prebuilt toolchains, can
> have debug paths that do not reflect paths within the local
> build directory. Providing an override lets us continue to use
> the standard debugedit logic in package.bbclass.
>
> Signed-off-by: Peter Seebach <peter.seeb...@windriver.com>
> ---
> meta/classes/package.bbclass | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
> index e6856cd..1a8c7f8 100644
> --- a/meta/classes/package.bbclass
> +++ b/meta/classes/package.bbclass
> @@ -191,6 +191,7 @@ def splitfile(file, debugfile, debugsrcdir, d):
> debugedit = d.expand("${STAGING_LIBDIR_NATIVE}/rpm/bin/debugedit")
> workdir = d.getVar("WORKDIR", True)
> workparentdir = os.path.dirname(workdir)
> + overridedir = d.getVar("DEBUGSRC_OVERRIDE_PATH", True) or ""
> sourcefile = d.expand("${WORKDIR}/debugsources.list")
I think I at least would find this slightly less confusing as:
workparentdir = d.getVar("DEBUGSRC_OVERRIDE_PATH", True) or
os.path.dirname(workdir)
Cheers,
Richard
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
