Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Christopher Larson <kergoth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: [PATCH 0/3] Fix a couple populate_sdk_ext issues
Date: Wed, 29 Jul 2015 14:53:54 -0700	[thread overview]
Message-ID: <cover.1438206555.git.chris_larson@mentor.com> (raw)

From: Christopher Larson <chris_larson@mentor.com>

- Explicitly pass BBPATH to devtool as Paul Eggleton suggests, to avoid
  needing to acquire the bitbake lock, to resolve the issue in
  populate_sdk_ext.
- Use the oe-core lnr script rather than ln -sr to improve host portability
  (not all hosts have recent coreutils).

The following changes since commit 27d068d05239c26a3848eb101571acab54635e37:

  harfbuzz: upgrade to 1.0.1 (2015-07-27 23:28:23 +0100)

are available in the git repository at:

  git@github.com:kergoth/openembedded-core populate_sdk_ext-fixes

for you to fetch changes up to a66090ba23452e0dca05e5811ebe88ea1bfc84de:

  populate_sdk_ext: pass BBPATH to devtool --bbpath (2015-07-29 14:48:05 -0700)

----------------------------------------------------------------
Christopher Larson (3):
      populate_sdk_ext: use lnr, not ln -sr, for portability
      devtool: add --bbpath argument
      populate_sdk_ext: pass BBPATH to devtool --bbpath

 meta/classes/populate_sdk_ext.bbclass |  7 ++++---
 scripts/devtool                       | 17 ++++++++++++-----
 2 files changed, 16 insertions(+), 8 deletions(-)

-- 
2.2.1



             reply	other threads:[~2015-07-29 21:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 21:53 Christopher Larson [this message]
2015-07-29 21:54 ` [PATCH 1/3] populate_sdk_ext: use lnr, not ln -sr, for portability Christopher Larson
2015-07-29 21:54 ` [PATCH 2/3] devtool: add --bbpath argument Christopher Larson
2015-07-29 21:54 ` [PATCH 3/3] populate_sdk_ext: pass BBPATH to devtool --bbpath Christopher Larson

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.1438206555.git.chris_larson@mentor.com \
    --to=kergoth@gmail.com \
    --cc=chris_larson@mentor.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