Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Extensible SDK improvements
Date: Wed,  2 Mar 2016 23:44:18 +1300	[thread overview]
Message-ID: <cover.1456915391.git.paul.eggleton@linux.intel.com> (raw)

Add ability to build derivative extensible SDK and fix up an issue with
the earlier patch introducing oe-workdir and oe-logs symlinks.


The following changes since commit 390bad905537820f49add855c95d726b5b55c8fa:

  sanity: Fix int verses string reference (2016-02-28 22:54:06 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/extsdkfixes8-oe
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/extsdkfixes8-oe

Paul Eggleton (3):
  classes/externalsrc: fix symlinking if symlink exists pointing to another path
  devtool: build-image: rename module
  devtool: add build-sdk subcommand

 meta/classes/externalsrc.bbclass                   |   1 +
 meta/classes/populate_sdk_ext.bbclass              | 148 +++++++++++++--------
 meta/lib/oe/copy_buildsystem.py                    |  59 +++++++-
 .../lib/devtool/{build-image.py => build_image.py} |  79 ++++++++---
 scripts/lib/devtool/build_sdk.py                   |  65 +++++++++
 5 files changed, 265 insertions(+), 87 deletions(-)
 rename scripts/lib/devtool/{build-image.py => build_image.py} (67%)
 create mode 100644 scripts/lib/devtool/build_sdk.py

-- 
2.5.0



             reply	other threads:[~2016-03-02 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 10:44 Paul Eggleton [this message]
2016-03-02 10:44 ` [PATCH 1/3] classes/externalsrc: fix symlinking if symlink exists pointing to another path Paul Eggleton
2016-03-02 10:44 ` [PATCH 2/3] devtool: build-image: rename module Paul Eggleton
2016-03-02 10:44 ` [PATCH 3/3] devtool: add build-sdk subcommand 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.1456915391.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