From: Hongxu Jia <hongxu.jia@windriver.com>
To: Mark Hatle <mark.hatle@windriver.com>, <ross.burton@intel.com>,
<richard.purdie@linuxfoundation.org>, <bruce.ashfield@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 01/15] conf/bitbake.conf package.bbclass: fix dbg package not contain sources while -fdebug-prefix-map used
Date: Wed, 23 Mar 2016 22:15:42 +0800 [thread overview]
Message-ID: <56F2A50E.9090102@windriver.com> (raw)
In-Reply-To: <56F29CC4.9010204@windriver.com>
On 03/23/2016 09:40 PM, Mark Hatle wrote:
> The following looks right to me. I'd recommend this version be used.
>
> However, I'm guessing the work is not done. Anything that has an ${S} outside
> of the WORKDIR will not be remapped. I'm guessing this includes the toolchain
> and kernel bits.... but other things might also have a shared work dir?
Yes, we should consider this situation, I will do the investigation to
find the fix
>
> We probably should make it a requirement that those things have their own unique
> mapping defined as well. I'm not sure if the existing tests will capture those
> issues and alert the user.
OK, with some investigation done, I will try to collect the requirements
for discussing.
>
> (This is also a place in the developer guide we should probably explain what
> this debug-prelix-map does and how it should be used to make on-target
> debuggable items.)
Maybe we should introduce -debug-pprefix-map in reference/development
manual, I will file a doc requirement in bugzilla.
So it's just a start, we should continue to work on:
1) Support to remap ${S} outside of the WORKDIR (shared work dir)
2) Add -fdebug-prefix-map usage in manual
//Hongxu
>
> --Mark
next prev parent reply other threads:[~2016-03-23 14:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 12:12 [PATCH V5 00/16] fix buildpaths QA issue Hongxu Jia
2016-03-22 12:12 ` [PATCH 01/16] conf/bitbake.conf package.bbclass: fix dbg package not contain sources while -fdebug-prefix-map used Hongxu Jia
2016-03-22 17:01 ` Mark Hatle
2016-03-23 1:11 ` Hongxu Jia
2016-03-22 12:12 ` [PATCH 02/16] kernel.bbclass: fix buildpath QA issue Hongxu Jia
2016-03-22 12:21 ` Bruce Ashfield
2016-03-22 16:18 ` Mark Hatle
2016-03-22 16:49 ` Bruce Ashfield
2016-03-22 16:57 ` Mark Hatle
2016-03-23 1:29 ` Hongxu Jia
2016-03-23 14:28 ` Bruce Ashfield
2016-03-23 15:50 ` Hongxu Jia
2016-03-22 12:12 ` [PATCH 03/16] dtc.inc: fix buildpaths " Hongxu Jia
2016-03-22 12:12 ` [PATCH 04/16] fix_buildpaths.bbclass: add bbclass to fix build path Hongxu Jia
2016-03-22 12:12 ` [PATCH 05/16] icu: fix buildpaths QA issue Hongxu Jia
2016-03-22 12:12 ` [PATCH 06/16] tcl: fix buildpath " Hongxu Jia
2016-03-22 12:12 ` [PATCH 07/16] python2/3: " Hongxu Jia
2016-03-22 12:12 ` [PATCH 08/16] bbclass distutils/distutils3: fix .pyc/.pyo buildpath Hongxu Jia
2016-03-22 12:12 ` [PATCH 09/16] bbclass distutils/distutils3/setuptools/setuptools3: clean up DISTUTILS_INSTALL_ARGS Hongxu Jia
2016-03-22 12:12 ` [PATCH 10/16] python-setuptools/python3-setuptools: use old-style install Hongxu Jia
2016-03-22 12:12 ` [PATCH 11/16] python3-pip: " Hongxu Jia
2016-03-22 12:12 ` [PATCH 12/16] waf.bbclass: support do patch on extracted files Hongxu Jia
2016-03-22 12:12 ` [PATCH 13/16] python-pycairo: fix buildpath QA issue Hongxu Jia
2016-03-22 12:12 ` [PATCH 14/16] openssl: " Hongxu Jia
2016-03-22 12:12 ` [PATCH 15/16] epiphany: fix buildpaths " Hongxu Jia
2016-03-22 12:12 ` [PATCH 16/16] gconf: " Hongxu Jia
2016-03-23 6:15 ` [PATCH V6 00/15] " Hongxu Jia
2016-03-23 6:15 ` [PATCH V2 01/15] conf/bitbake.conf package.bbclass: fix dbg package not contain sources while -fdebug-prefix-map used Hongxu Jia
2016-03-23 13:40 ` Mark Hatle
2016-03-23 14:15 ` Hongxu Jia [this message]
2016-03-23 6:15 ` [PATCH 03/15] fix_buildpaths.bbclass: add bbclass to fix build path Hongxu Jia
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=56F2A50E.9090102@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@intel.com \
/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