From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/16] Simplify how to stage directories in the sysroot
Date: Thu, 12 May 2016 08:18:47 +0000 [thread overview]
Message-ID: <225f61b6fefa4aebbc7d99d66cfa4fac@XBOX02.axis.com> (raw)
In-Reply-To: <1463002482.21831.291.camel@linuxfoundation.org>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of Richard Purdie
> Sent: den 11 maj 2016 23:35
> To: Peter Kjellerstedt; openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 00/16] Simplify how to stage directories in the sysroot
>
> On Wed, 2016-05-11 at 19:27 +0200, Peter Kjellerstedt wrote:
> > 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...
>
> It matches binaries that can run on the build system so it needs to
> match native and cross. Something like:
>
> SYSROOT_DIRS_append_class-native = "${SYSROOT_DIRS_NATIVE}"
> SYSROOT_DIRS_append_class-cross = "${SYSROOT_DIRS_NATIVE}"
Apparently it is true for crossssdk as well (I ran recipes from each of
the five classes through bitbake -e to verify). I will send an updated
patch that uses the _append solution instead.
> I hadn't realised how much duplication there was in that class. Cleanup
> I'd never gotten around to doing. I guess most people don't even
> remember how we ended up with that code or the horrors of do_stage
> functions :)
I looked at some of the horrors in the git log while investigating how
it works. I am glad you got rid of them. ;)
> Cheers,
>
> Richard
//Peter
prev parent reply other threads:[~2016-05-12 8:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 17:27 [PATCH 00/16] Simplify how to stage directories in the sysroot Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 01/16] staging.bbclass: Make it easier to define which dirs to stage Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 02/16] u-boot-fw-utils: Use SYSROOT_DIRS to add dirs to stage in sysroot Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 03/16] libtool-cross: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 04/16] qemuwrapper-cross: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 05/16] tcl: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 06/16] shadow-sysroot: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 07/16] depmodwrapper-cross: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 08/16] base-files: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 09/16] signing-keys: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 10/16] vala.inc: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 11/16] gobject-introspection: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 12/16] grub2.inc: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from the sysroot Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 13/16] gettext: " Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 14/16] gcc-target.inc: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from sysroot Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 15/16] libtool: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from the sysroot Peter Kjellerstedt
2016-05-11 17:27 ` [PATCH 16/16] font-util: Remove ${datadir}/fonts from SYSROOT_DIRS_BLACKLIST Peter Kjellerstedt
2016-05-11 21:34 ` [PATCH 00/16] Simplify how to stage directories in the sysroot Richard Purdie
2016-05-12 8:18 ` Peter Kjellerstedt [this message]
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=225f61b6fefa4aebbc7d99d66cfa4fac@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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