From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCHv2 00/16] Simplify how to stage directories in the sysroot
Date: Thu, 12 May 2016 10:37:47 +0200 [thread overview]
Message-ID: <cover.1463042237.git.pkj@axis.com> (raw)
The first commit in this set makes it possible to specify the
directories that will be staged in the sysroot via variables rather
than hardcoding it in sysroot_stage_dirs(). This should make it a lot
easier to add/remove directories to stage.
The rest of the commits just change recipes to take advantage of the
new variables.
Because of the following if statement in sysroot_stage_dirs():
if [ "${BUILD_SYS}" = "${HOST_SYS}" ]; then
I have split the list of directories into SYSROOT_DIRS and
SYSROOT_DIRS_NATIVE, where the latter is included if that if statement
is true. I am not sure when that statement is true (my understanding
is that it should be true for native builds, but I am not sure if it
is also true for other builds like cross, nativesdk, etc). If it is
only true for native builds then that if statement could be removed,
and the SYSROOT_DIRS_NATIVE variable could be replaced by
SYSROOT_DIRS_append_class-native...
PATCHv2: Removed the if statement mentioned above and replaced it with
normal _append operations on SYSROOT_DIRS instead.
//Peter
The following changes since commit 28433319ad8299aa23b1fcfdddbe100b29e86517:
bitbake: toaster: tests browser Add test for creating a project (2016-05-11 11:32:58 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib pkj/sysroot_dirs
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/sysroot_dirs
Peter Kjellerstedt (16):
staging.bbclass: Make it easier to define which dirs to stage
u-boot-fw-utils: Use SYSROOT_DIRS to add dirs to stage in sysroot
libtool-cross: Use SYSROOT_DIRS to add dirs to stage in sysroot
qemuwrapper-cross: Use SYSROOT_DIRS to add dirs to stage in sysroot
tcl: Use SYSROOT_DIRS to add dirs to stage in sysroot
shadow-sysroot: Use SYSROOT_DIRS to add dirs to stage in sysroot
depmodwrapper-cross: Use SYSROOT_DIRS to add dirs to stage in sysroot
base-files: Use SYSROOT_DIRS to add dirs to stage in sysroot
signing-keys: Use SYSROOT_DIRS to add dirs to stage in sysroot
vala.inc: Use SYSROOT_DIRS to add dirs to stage in sysroot
gobject-introspection: Use SYSROOT_DIRS to add dirs to stage in
sysroot
grub2.inc: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from the sysroot
gettext: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from the sysroot
gcc-target.inc: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from
sysroot
libtool: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from the sysroot
font-util: Remove ${datadir}/fonts from SYSROOT_DIRS_BLACKLIST
meta/classes/staging.bbclass | 75 ++++++++++++----------
meta/recipes-bsp/grub/grub2.inc | 5 +-
meta/recipes-bsp/u-boot/u-boot-fw-utils_2016.03.bb | 5 +-
meta/recipes-core/base-files/base-files_3.0.14.bb | 5 +-
meta/recipes-core/gettext/gettext_0.16.1.bb | 7 +-
meta/recipes-core/meta/signing-keys.bb | 6 +-
meta/recipes-devtools/gcc/gcc-target.inc | 4 +-
.../libtool/libtool-cross_2.4.6.bb | 7 +-
meta/recipes-devtools/libtool/libtool_2.4.6.bb | 13 ++--
.../recipes-devtools/qemu/qemuwrapper-cross_1.0.bb | 6 +-
meta/recipes-devtools/tcltk/tcl_8.6.4.bb | 5 +-
meta/recipes-devtools/vala/vala.inc | 13 ++--
.../shadow/shadow-sysroot_4.2.1.bb | 6 +-
.../gobject-introspection_1.46.0.bb | 9 ++-
meta/recipes-graphics/xorg-font/font-util_1.3.1.bb | 5 +-
.../recipes-kernel/kmod/depmodwrapper-cross_1.0.bb | 6 +-
16 files changed, 71 insertions(+), 106 deletions(-)
--
2.1.0
next reply other threads:[~2016-05-12 8:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 8:37 Peter Kjellerstedt [this message]
2016-05-12 8:37 ` [PATCHv2 01/16] staging.bbclass: Make it easier to define which dirs to stage Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 02/16] u-boot-fw-utils: Use SYSROOT_DIRS to add dirs to stage in sysroot Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 03/16] libtool-cross: " Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 04/16] qemuwrapper-cross: " Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 05/16] tcl: " Peter Kjellerstedt
2016-05-26 12:00 ` Andreas Müller
2016-05-26 13:41 ` Peter Kjellerstedt
2016-05-26 15:33 ` Martin Jansa
2016-05-26 20:14 ` Andreas Müller
2016-05-28 13:41 ` Andreas Müller
2016-05-31 9:02 ` Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 06/16] shadow-sysroot: " Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 07/16] depmodwrapper-cross: " Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 08/16] base-files: " Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 09/16] signing-keys: " Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 10/16] vala.inc: " Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 11/16] gobject-introspection: " Peter Kjellerstedt
2016-05-12 8:37 ` [PATCHv2 12/16] grub2.inc: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from the sysroot Peter Kjellerstedt
2016-05-12 8:38 ` [PATCHv2 13/16] gettext: " Peter Kjellerstedt
2016-05-12 8:38 ` [PATCHv2 14/16] gcc-target.inc: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from sysroot Peter Kjellerstedt
2016-05-12 8:38 ` [PATCHv2 15/16] libtool: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from the sysroot Peter Kjellerstedt
2016-05-12 8:38 ` [PATCHv2 16/16] font-util: Remove ${datadir}/fonts from SYSROOT_DIRS_BLACKLIST 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.1463042237.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