From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] cross-canadian.bbclass: Add BASECANADIANEXTRAOS to specify main extraos
Date: Mon, 7 Dec 2015 15:39:29 -0600 [thread overview]
Message-ID: <5665FC91.1050803@windriver.com> (raw)
In-Reply-To: <1449524171-2835-1-git-send-email-mark.hatle@windriver.com>
Sorry forgot to setup a cover letter.
The issue is that various extra OS entries cause numerous symlinks to be set.
These symlinks can cause confusion for someone looking in the directory. They
may think uclibc or musl is actually supported.
However, the real problem is when you build an SDK for Windows (mingw), symlinks
get expanded on installation. So you end up with a full copy of the toolchain
for each symlink.
This will increase (the installed) size of the x86_64 toolchain by 600MB, for no
real reason.
The change is equally applicable to master and jethro.
On 12/7/15 3:36 PM, Mark Hatle wrote:
> By default the system will expand the extra os entries for uclibc and musl
> even if they are not enabled in the build. There was no way to prevent this
> behavior while still getting the expansion for things like x32 or spe.
>
> The change adds a new setting which a distribution creator can override
> easily, setting the base set of canadianextraos components. The other
> expansions are then based on this setting.
>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
> meta/classes/cross-canadian.bbclass | 22 +++++++++++++++++-----
> 1 file changed, 17 insertions(+), 5 deletions(-)
>
next prev parent reply other threads:[~2015-12-07 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 21:36 [PATCH] cross-canadian.bbclass: Add BASECANADIANEXTRAOS to specify main extraos Mark Hatle
2015-12-07 21:39 ` Mark Hatle [this message]
2016-08-10 5:34 ` Huang, Jie (Jackie)
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=5665FC91.1050803@windriver.com \
--to=mark.hatle@windriver.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