From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/8] Extensible SDK improvements
Date: Sat, 23 Jul 2016 00:38:06 +1200 [thread overview]
Message-ID: <cover.1469190931.git.paul.eggleton@linux.intel.com> (raw)
Some fixes and enhancements centered around how the toolchain is
incorporated in the eSDK, as well as a couple of tweaks for buildhistory
that I found we needed during development.
Note: this is on top of my earlier as-yet unmerged eSDK progress patch.
The following changes since commit 7e4a33933d39f6406922231d64414637a5f52d66:
classes/populate_sdk_ext: show progress when preparing build system (2016-07-23 00:34:44 +1200)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/extsdkfixes12-oe
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/extsdkfixes12-oe
Paul Eggleton (8):
classes/populate_sdk_ext: set default for SDK_INCLUDE_PKGDATA
meta-extsdk-toolchain: add meta-recipe to install toolchain into eSDK
classes/populate_sdk_ext: allow including toolchain in eSDK on install
scripts: add oe-check-sstate script
classes/populate_sdk_ext: filter sstate within the extensible SDK
classes/populate_sdk_ext: add gdb to full extensible SDK
classes/buildhistory: add additional variables for eSDK
classes/buildhistory: ensure eSDK sstate lists sorted secondarily by name
meta/classes/buildhistory.bbclass | 6 +-
meta/classes/populate_sdk_ext.bbclass | 92 +++++++++++++++++-
meta/classes/sstate.bbclass | 3 +
meta/lib/oe/copy_buildsystem.py | 27 +++++-
meta/recipes-core/meta/meta-extsdk-toolchain.bb | 28 ++++++
scripts/gen-lockedsig-cache | 16 +++-
scripts/oe-check-sstate | 121 ++++++++++++++++++++++++
7 files changed, 280 insertions(+), 13 deletions(-)
create mode 100644 meta/recipes-core/meta/meta-extsdk-toolchain.bb
create mode 100755 scripts/oe-check-sstate
--
2.5.5
next reply other threads:[~2016-07-22 12:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 12:38 Paul Eggleton [this message]
2016-07-22 12:38 ` [PATCH 1/8] classes/populate_sdk_ext: set default for SDK_INCLUDE_PKGDATA Paul Eggleton
2016-07-22 12:38 ` [PATCH 2/8] meta-extsdk-toolchain: add meta-recipe to install toolchain into eSDK Paul Eggleton
2016-07-22 12:38 ` [PATCH 3/8] classes/populate_sdk_ext: allow including toolchain in eSDK on install Paul Eggleton
2016-07-22 12:38 ` [PATCH 4/8] scripts: add oe-check-sstate script Paul Eggleton
2016-07-22 12:38 ` [PATCH 5/8] classes/populate_sdk_ext: filter sstate within the extensible SDK Paul Eggleton
2016-07-25 8:41 ` [PATCH v2] " Paul Eggleton
2016-07-22 12:38 ` [PATCH 6/8] classes/populate_sdk_ext: add gdb to full " Paul Eggleton
2016-07-22 12:38 ` [PATCH 7/8] classes/buildhistory: add additional variables for eSDK Paul Eggleton
2016-07-22 12:38 ` [PATCH 8/8] classes/buildhistory: ensure eSDK sstate lists sorted secondarily by name Paul Eggleton
2016-07-22 22:31 ` [PATCH 0/8] Extensible SDK improvements Burton, Ross
2016-07-23 1:11 ` Paul Eggleton
2016-07-24 21:42 ` Paul Eggleton
2016-07-24 23:31 ` Khem Raj
2016-07-24 23:45 ` Paul Eggleton
2016-07-25 16:39 ` Burton, Ross
2016-07-25 20:33 ` Paul Eggleton
2016-07-25 20:38 ` Burton, Ross
2016-07-25 7:42 ` Paul Eggleton
2016-07-29 7:26 ` Richard Purdie
2016-07-30 10:01 ` Paul Eggleton
2016-08-01 1:35 ` 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.1469190931.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.