From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/7][RFC][HEREBEDRAGONS] Remove bitbake's knowledge of ${B}
Date: Mon, 13 Jul 2015 15:02:58 +0100 [thread overview]
Message-ID: <cover.1436795781.git.ross.burton@intel.com> (raw)
Hi,
So when starting a new task if you don't tell bitbake what directories it should
create (and implicit, chdir() into) it uses ${B}. Which is bitbake knowing
about openembedded variables, and generally frowned upon.
This branch series removes that knowledge, and if a task is executed without any
directories to create or chdir into it just doesn't do anything.
This revealed a few classes and recipes which assume they're being ran in ${B}
so the rest of the series is either adding back [dirs] flags to the tasks, or
making paths absolute.
Testing has been quite minimal: core-image-sato builds but I've not verified the
contents haven't changed yet.
Comments?
Ross
The following changes since commit 7f8286fb9ec9f9d9f606c69e5abd717078ace5b2:
classes/sstate.bbclass: Improve checkstatus using connection cache. (2015-07-12 22:55:46 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ross/dirs
for you to fetch changes up to b306a4b740868835ff0e0ac14d8b7ed9afe83091:
kernel: fix path assumptions (2015-07-13 14:51:57 +0100)
----------------------------------------------------------------
Ross Burton (7):
build: don't automatically mkdir/chdir B
build: add remove/mkdir/chdir debugging
ptest: add dirs
boost: add dirs
python: add explicit directory when copying
libc-package: fix path assumption
kernel: fix path assumptions
bitbake/lib/bb/build.py | 19 ++++++++++++++++++-
meta/classes/kernel.bbclass | 8 ++++----
meta/classes/libc-package.bbclass | 3 +--
meta/classes/ptest.bbclass | 3 +++
meta/recipes-devtools/python/python3_3.4.3.bb | 2 +-
meta/recipes-devtools/python/python_2.7.9.bb | 2 +-
meta/recipes-support/boost/boost.inc | 1 +
7 files changed, 29 insertions(+), 9 deletions(-)
Ross Burton (7):
build: don't automatically mkdir/chdir B
build: add remove/mkdir/chdir debugging
ptest: add dirs
boost: add dirs
python: add explicit directory when copying
libc-package: fix path assumption
kernel: fix path assumptions
bitbake/lib/bb/build.py | 19 ++++++++++++++++++-
meta/classes/kernel.bbclass | 8 ++++----
meta/classes/libc-package.bbclass | 3 +--
meta/classes/ptest.bbclass | 3 +++
meta/recipes-devtools/python/python3_3.4.3.bb | 2 +-
meta/recipes-devtools/python/python_2.7.9.bb | 2 +-
meta/recipes-support/boost/boost.inc | 1 +
7 files changed, 29 insertions(+), 9 deletions(-)
--
2.1.4
next reply other threads:[~2015-07-13 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 14:02 Ross Burton [this message]
2015-07-13 14:02 ` [PATCH 1/7] build: don't automatically mkdir/chdir B Ross Burton
2015-07-13 14:03 ` [PATCH 2/7] build: add remove/mkdir/chdir debugging Ross Burton
2015-07-13 14:03 ` [PATCH 3/7] ptest: add dirs Ross Burton
2015-07-13 14:03 ` [PATCH 4/7] boost: " Ross Burton
2015-07-13 14:03 ` [PATCH 5/7] python: add explicit directory when copying Ross Burton
2015-07-13 14:03 ` [PATCH 6/7] libc-package: fix path assumption Ross Burton
2015-07-13 14:38 ` Christopher Larson
2015-07-13 14:39 ` Burton, Ross
2015-07-13 14:03 ` [PATCH 7/7] kernel: fix path assumptions Ross Burton
2015-07-14 11:03 ` [PATCH 0/7][RFC][HEREBEDRAGONS] Remove bitbake's knowledge of ${B} Burton, Ross
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.1436795781.git.ross.burton@intel.com \
--to=ross.burton@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