From: Kang Kai <Kai.Kang@windriver.com>
To: "Hatle, Mark" <mark.hatle@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: About minimal image
Date: Tue, 26 Apr 2011 13:40:06 +0800 [thread overview]
Message-ID: <4DB65AB6.4040208@windriver.com> (raw)
In-Reply-To: <4DB620F5.3010709@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
Hi Mark,
> I have read your mail about minimal image posted on Feb 19 on this
> mail list. We try to reduce image size by what your said:
>
> 1. eglic configurability
> 2. using mklibs
>
>
> Right now after migrate eglic configurability to my local yocto
> branch, and I only enable 4 options ("locale-code nsswitch rtld-debug
> posix-clang-wchar ", pls. check in attachment) of eglibc just to make
> compile pass.
>
> When after create minimal image, the rootfs (tar.bz2) is still about
> 3.4M, same size as without adding configurability to eglibc.
>
> Could you give me some directions what should we do in next step? We
> also hope some information about how to use mklibs to reduce packages
> and image size?
After open MKLIBS_OPTIMIZED_IMAGES ?= "core-image-minimal" in
local.conf, the minimal image decrease from 3.4M to 3.1M, after
extraction is 8.1M( vs. 8.4M before using mklibs). It looks like not so
efficient as we expected.
Should I try to reduce busybox size at same time?Such as remove some not
so usually used commands by configurations?
Any suggestion or guild will be appreciate!
Thanks and Regards,
Kai
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
[-- Attachment #2: Type: text/html, Size: 2254 bytes --]
next prev parent reply other threads:[~2011-04-26 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 3:10 About minimal image Kang Kai
2011-04-26 1:33 ` Kang Kai
2011-04-26 5:40 ` Kang Kai [this message]
2011-04-26 17:41 ` Mark Hatle
2011-04-27 1:55 ` Kang Kai
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=4DB65AB6.4040208@windriver.com \
--to=kai.kang@windriver.com \
--cc=mark.hatle@windriver.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.