From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] Extensible SDK fixes
Date: Thu, 11 Aug 2016 16:44:57 +1200 [thread overview]
Message-ID: <cover.1470890478.git.paul.eggleton@linux.intel.com> (raw)
Fixes for building the extensible SDK without uninative enabled, fixes
for the recently implemented sstate filtering, fixes for buildtools
handling within the eSDK installer, addition of sanity tests early in
the eSDK install process, and a couple of other related fixes.
Worth noting is that this changeset, building the eSDK with OE-Core's
default configuration now works again. It's not clear to me when it
broke (it may have only been recently, certainly it was after the
sstate filtering patches that the YP autobuilder started warning that
the tests were failing with OE-Core).
The following changes since commit 5ed0d5a7d9b051a551a6de644bf6a42b87c12471:
dbus: backport stdint.h build fix (2016-08-10 10:45:33 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/extsdkfixes13-oe
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/extsdkfixes13-oe
Paul Eggleton (10):
gen-lockedsig-cache: ensure symlinks are dereferenced
classes/populate_sdk_ext: ensure eSDK can build without uninative enabled
classes/populate_sdk_ext: handle lack of uninative when filtering sstate
classes/populate_sdk_ext: sstate filtering fixes
lib/oe/copy_buildsystem: fix merging sstate directories for eSDK
classes/populate_sdk_ext: properly handle buildtools install failure
classes/populate_sdk_ext: properly determine buildtools filename
toolchain-shar-extract.sh: add option to list contents
classes/populate_sdk_ext: add some pre-install checks
classes/populate_sdk_ext: drop duplicated error message
meta/classes/populate_sdk_ext.bbclass | 114 +++++++++++++++++++++++++++-------
meta/files/ext-sdk-prepare.py | 2 +-
meta/files/toolchain-shar-extract.sh | 25 +++++++-
meta/lib/oe/copy_buildsystem.py | 20 +++---
scripts/gen-lockedsig-cache | 7 ++-
5 files changed, 131 insertions(+), 37 deletions(-)
--
2.5.5
next reply other threads:[~2016-08-11 4:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 4:44 Paul Eggleton [this message]
2016-08-11 4:44 ` [PATCH 01/10] gen-lockedsig-cache: ensure symlinks are dereferenced Paul Eggleton
2016-08-11 4:44 ` [PATCH 02/10] classes/populate_sdk_ext: ensure eSDK can build without uninative enabled Paul Eggleton
2016-08-11 4:45 ` [PATCH 03/10] classes/populate_sdk_ext: handle lack of uninative when filtering sstate Paul Eggleton
2016-08-11 4:45 ` [PATCH 04/10] classes/populate_sdk_ext: sstate filtering fixes Paul Eggleton
2016-08-11 4:45 ` [PATCH 05/10] lib/oe/copy_buildsystem: fix merging sstate directories for eSDK Paul Eggleton
2016-08-11 4:45 ` [PATCH 06/10] classes/populate_sdk_ext: properly handle buildtools install failure Paul Eggleton
2016-08-11 4:45 ` [PATCH 07/10] classes/populate_sdk_ext: properly determine buildtools filename Paul Eggleton
2016-08-11 4:45 ` [PATCH 08/10] toolchain-shar-extract.sh: add option to list contents Paul Eggleton
2016-08-11 4:45 ` [PATCH 09/10] classes/populate_sdk_ext: add some pre-install checks Paul Eggleton
2016-08-11 22:47 ` Paul Eggleton
2016-08-11 4:45 ` [PATCH 10/10] classes/populate_sdk_ext: drop duplicated error message Paul Eggleton
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.1470890478.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.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