From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] package.bbclass: improve auto debug package splitting order
Date: Fri, 14 Sep 2018 16:49:39 +0800 [thread overview]
Message-ID: <cover.1536913629.git.hongxu.jia@windriver.com> (raw)
Hi RP,
Is it necessary to split multiple sub dbg packages or only
one dbg is allowed? If the former, this fix makes sense.
I know in oe-core, almost one dbg package per recipe, but
in oe, 21 recipes have extra sub dbg package and 18 of them
did not set NOAUTOPACKAGEDEBUG = "1".
So rather than modify them one by one tediously, how about to
improve auto debug package splitting order? If ${PN}-dbg exists,
split the unsplit debug file to ${PN}-dbg, if ${PN}-dbg does not
exist, still split them to first dbg package.
//Hongxu
The following changes since commit d180dc758710c7259d45eeb9304e7284a8fd8825:
oeqa/selftest/recipetool: fix non-determinism in cmake test (2018-09-13 16:28:26 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib hongxu/dbg-split
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=hongxu/dbg-split
Hongxu Jia (2):
package.bbclass: improve auto debug package splitting order
selftest/package: improve case to test debug package splitting
.../selftest-hardlink/selftest-hardlink.bb | 4 +++-
meta/classes/package.bbclass | 10 +++++++-
meta/lib/oeqa/selftest/cases/package.py | 27 ++++++++++++++++------
3 files changed, 32 insertions(+), 9 deletions(-)
--
2.7.4
next reply other threads:[~2018-09-14 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:49 Hongxu Jia [this message]
2018-09-14 8:49 ` [PATCH 1/2] package.bbclass: improve auto debug package splitting order Hongxu Jia
2018-09-14 8:49 ` [PATCH 2/2] selftest/package: improve case to test debug package splitting Hongxu Jia
2018-09-14 12:06 ` [PATCH V2 " Hongxu Jia
2018-09-17 11:51 ` [PATCH 0/2] package.bbclass: improve auto debug package splitting order Hongxu Jia
2018-09-17 12:06 ` richard.purdie
2018-09-17 12:18 ` 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=cover.1536913629.git.hongxu.jia@windriver.com \
--to=hongxu.jia@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