From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Andreas Müller" <schnitzeltony@googlemail.com>,
"Hongxu Jia" <hongxu.jia@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 01/17] conf/bitbake.conf package.bbclass: fix dbg package not contain sources while -fdebug-prefix-map used
Date: Tue, 19 Apr 2016 15:54:08 +0100 [thread overview]
Message-ID: <1461077648.31320.15.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALbNGRQB-BUVH6qcQxey9CYOji-z8ydVA==qi5bx-ouBVpGaWw@mail.gmail.com>
On Tue, 2016-04-19 at 16:11 +0200, Andreas Müller wrote:
> thanks a lot for your efforts. Do I understand this right: You
> suggest
> to use build sysroot (on my own risk - as I did before) and make gdb
> happy by linking sources?
>
> Problem I see is that we have multiple package archs e.g
> ARM/ARMThumb/Machine so ${BASE_WORKDIR}/${MULTIMACH_TARGET_SYS}
> expands to multiple paths. But a script symlinking all together + set
> substitute-path might help here...
>
> I will play around with this in the later...
I was thinking about this a bit more and there is another option
available to you which would be to pass all the debug sources into the
sysroot as hardlinks to the files in workdir, in much the same way as
we do the other sysroot files (which you don't strip).
Since those files are collected by do_package you'd probably have to
force do_populate_sysroot after do_package but such an additional class
to make these tweaks probably wouldn't be that large and would just
affect performance a bit (with the benefit of the debugging you want).
Just thinking out loud really. My big worry is all the different
codepaths we have people using, equally, you can't get performance
(disk footprint and speed) and functionality in some cases and people
do want to choose different compromises.
Cheers,
Richard
next prev parent reply other threads:[~2016-04-19 14:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 8:18 [PATCH V7 00/17] fix buildpaths QA issue && dbp package source generation Hongxu Jia
2016-03-28 8:18 ` [PATCH 01/17] conf/bitbake.conf package.bbclass: fix dbg package not contain sources while -fdebug-prefix-map used Hongxu Jia
2016-04-18 8:09 ` Andreas Müller
2016-04-18 8:11 ` Hongxu Jia
2016-04-18 8:23 ` Andreas Müller
2016-04-18 8:32 ` Hongxu Jia
2016-04-18 8:47 ` Andreas Müller
2016-04-18 9:04 ` Hongxu Jia
2016-04-18 9:15 ` Andreas Müller
2016-04-18 9:34 ` Hongxu Jia
2016-04-18 9:52 ` Andreas Müller
2016-04-18 13:08 ` Hongxu Jia
2016-04-18 13:55 ` Burton, Ross
2016-04-18 14:16 ` Andreas Müller
2016-04-18 14:51 ` Richard Purdie
2016-04-18 18:50 ` Mark Hatle
2016-04-18 21:05 ` Andreas Müller
2016-04-19 0:51 ` Mark Hatle
2016-04-19 4:32 ` Paul Eggleton
2016-04-19 12:29 ` Mark Hatle
2016-04-19 7:33 ` Hongxu Jia
2016-04-19 12:31 ` Mark Hatle
2016-04-19 12:59 ` Hongxu Jia
2016-04-19 14:11 ` Andreas Müller
2016-04-19 14:47 ` Mark Hatle
2016-04-19 14:49 ` Mark Hatle
2016-04-19 14:54 ` Richard Purdie [this message]
2016-04-19 21:50 ` Andreas Müller
2016-04-28 21:41 ` Andreas Müller
2016-04-19 1:46 ` Hongxu Jia
2016-03-28 8:18 ` [PATCH 02/17] gcc-5.3/gcc-4.9: -fdebug-prefix-map support to remap relative path Hongxu Jia
2016-03-28 8:18 ` [PATCH 03/17] conf/bitbake.conf package.bbclass: improve dbg package sources generation from work-shared Hongxu Jia
2016-03-29 22:38 ` Richard Purdie
2016-03-30 1:58 ` Hongxu Jia
2016-03-30 5:36 ` Hongxu Jia
2016-03-28 8:18 ` [PATCH 04/17] dtc.inc: fix buildpaths QA issue Hongxu Jia
2016-03-28 8:18 ` [PATCH 05/17] fix_buildpaths.bbclass: add bbclass to fix build path Hongxu Jia
2016-03-28 8:18 ` [PATCH 06/17] icu: fix buildpaths QA issue Hongxu Jia
2016-03-28 8:18 ` [PATCH 07/17] tcl: fix buildpath " Hongxu Jia
2016-03-28 8:18 ` [PATCH 08/17] python2/3: " Hongxu Jia
2016-03-28 8:18 ` [PATCH 09/17] bbclass distutils/distutils3: fix .pyc/.pyo buildpath Hongxu Jia
2016-03-28 8:18 ` [PATCH 10/17] bbclass distutils/distutils3/setuptools/setuptools3: clean up DISTUTILS_INSTALL_ARGS Hongxu Jia
2016-03-28 8:18 ` [PATCH 11/17] python-setuptools/python3-setuptools: use old-style install Hongxu Jia
2016-03-28 8:18 ` [PATCH 12/17] python3-pip: " Hongxu Jia
2016-03-28 8:18 ` [PATCH 13/17] waf.bbclass: support do patch on extracted files Hongxu Jia
2016-03-28 8:18 ` [PATCH 14/17] python-pycairo: fix buildpath QA issue Hongxu Jia
2016-03-28 8:18 ` [PATCH 15/17] openssl: " Hongxu Jia
2016-03-28 8:19 ` [PATCH 16/17] epiphany: fix buildpaths " Hongxu Jia
2016-03-28 8:19 ` [PATCH 17/17] ifupdown: fix do_compile failed while GCCVERSION = "4.9%" Hongxu Jia
2016-03-30 8:06 ` [PATCH V7 00/17] fix buildpaths QA issue && dbp package source generation 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=1461077648.31320.15.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@googlemail.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