Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCHv2 0/7] Improve oe-init-build-env/-memres
Date: Thu, 17 Mar 2016 12:14:07 +0100	[thread overview]
Message-ID: <cover.1458213205.git.pkj@axis.com> (raw)

I started looking at the oe-init-build-env (and
oe-init-build-env-memres) scripts since I wanted to add support for
specifying $OEROOT from the outside. This is because we want to wrap
those scripts with our own while keeping the official names (so anyone
reading the official Poky documentation will not be too confused).

While fixing the above, I had noticed a number of inconsistencies in
the scripts, so I continued to fix those. I also improved the code
that adds paths to $PATH, and the code that adds variable names to
$BB_ENV_EXTRAWHITE.

New in version 2:

* Make sure oe-init-build-env and oe-init-build-env-memres actually
  return failures from other scripts they source and call.

//Peter

The following changes since commit 8debfea81e69d038bd2d56314b272cb74f5582ed:

  local.conf.sample: Disable prelink by default (2016-03-13 22:09:05 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib pkj/oe-init-build-env
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/oe-init-build-env

Peter Kjellerstedt (7):
  oe-init-build-env*: Allow $OEROOT to be predefined
  oe-init-build-env*: Update/correct comment about specifying arguments
  oe-init-build-env*: Remove unnecessary differences between the scripts
  oe-init-build-env*: Make them actually return failures
  oe-buildenv-internal: Add paths to $PATH individually
  oe-buildenv-internal: Add variables individually to BB_ENV_EXTRAWHITE
  oe-buildenv-internal: Some clean up

 oe-init-build-env            | 51 +++++++++++++++------------
 oe-init-build-env-memres     | 60 ++++++++++++++++++--------------
 scripts/oe-buildenv-internal | 83 ++++++++++++++++++++++++++++----------------
 3 files changed, 114 insertions(+), 80 deletions(-)

-- 
2.1.0



             reply	other threads:[~2016-03-17 11:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 11:14 Peter Kjellerstedt [this message]
2016-03-17 11:14 ` [PATCHv2 1/7] oe-init-build-env*: Allow $OEROOT to be predefined Peter Kjellerstedt
2016-03-17 11:14 ` [PATCHv2 2/7] oe-init-build-env*: Update/correct comment about specifying arguments Peter Kjellerstedt
2016-03-17 11:14 ` [PATCHv2 3/7] oe-init-build-env*: Remove unnecessary differences between the scripts Peter Kjellerstedt
2016-03-17 11:14 ` [PATCHv2 4/7] oe-init-build-env*: Make them actually return failures Peter Kjellerstedt
2016-03-17 11:14 ` [PATCHv2 5/7] oe-buildenv-internal: Add paths to $PATH individually Peter Kjellerstedt
2016-03-17 11:14 ` [PATCHv2 6/7] oe-buildenv-internal: Add variables individually to BB_ENV_EXTRAWHITE Peter Kjellerstedt
2016-03-17 11:14 ` [PATCHv2 7/7] oe-buildenv-internal: Some clean up Peter Kjellerstedt
2016-03-21 10:09 ` [PATCHv2 0/7] Improve oe-init-build-env/-memres Robert Yang
2016-03-21 11:55   ` Peter Kjellerstedt

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.1458213205.git.pkj@axis.com \
    --to=peter.kjellerstedt@axis.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