Bug 6651

Summary:	Trim size of extensible SDK
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Paul Eggleton <bluelightning>
Component:	devtools / tool chain	Assignee:	Randy Witt <randy.e.witt>
Status:	RESOLVED FIXED	QA Contact:	Aníbal Limón <anibal.limon>
Severity:	enhancement
Priority:	Medium+	CC:	alexander.kanevskiy, alexandru.c.georgescu, dmitry.rojkov, meta.mr.watcher, meta.watcher, Qi.Chen
Version:	1.7
Target Milestone:	2.1 M2
Hardware:	All
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know
Bug Depends on:
Bug Blocks:	8789

Description Paul Eggleton 2014-08-22 15:56:54 UTC

We need to examine what sstate artifacts we need to go into constructing the SDK when it contains the build system; if we simply use task dependencies as set up at the moment just to be able to build core-image-minimal we end up with something that is ~1.5GB compressed (i.e. composed of the host part of the SDK + metadata + sstate artifacts). We should try to reduce this if at all possible. (This may also be about deciding how we specify the SDK capabilities / contents, so that the user can tailor the SDK to their requirements.)

Comment 1 Paul Eggleton 2015-04-29 13:12:33 UTC

Clarification - this applies to the extensible SDK (bitbake -c populate_sdk_ext)

Comment 2 Paul Eggleton 2015-10-28 11:57:57 UTC

There are a few different configurations I can think of:

1) The current mode, where you get all of the artifacts required to do a build against something in the image

2) "Light" mode where you get do_populate_sysroot executed for the toolchain and all of the recipes for the packages in the image

3) Maybe a "super-light" mode where you get just the toolchain?

(we probably want better switch naming than "light" / "super-light" etc.)

With all of these we have the option of having SSTATE_MIRRORS set so that sstate archives can be pulled in from a server as needed, at least for building images and packages that will work automatically.

Note: during ext SDK construction if we know we aren't including the full sstate for the image and SSTATE_MIRRORS isn't set in the local.conf file we've created, we should configure devtool to hide or disable the build-image and package subcommands since they won't be usable.

Comment 3 Paul Eggleton 2015-12-11 01:26:55 UTC

I've split off that last paragraph to a new bug - bug 8789 - so that this one can be dedicated to just providing the means to cut down the size of the extensible SDK.

Comment 4 Randy Witt 2016-02-10 20:46:19 UTC

Should be fixed with

commit 4f7656a2047f4f67c3965693c3ca9f94e634cd9d
Author: Randy Witt <randy.e.witt@linux.intel.com>
Date:   Thu Feb 4 12:31:44 2016 -0800

https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=4f7656a2047f4f67c3965693c3ca9f94e634cd9d