From: nick <xerofoify@gmail.com>
To: Diego Sueiro <diego.sueiro@gmail.com>,
Ross Burton <ross.burton@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Build optimization question
Date: Sat, 08 Nov 2014 23:27:07 -0500 [thread overview]
Message-ID: <545EED1B.5030203@gmail.com> (raw)
In-Reply-To: <CAMCfZKEXVDcd44Yf4AOdKWcYd7UOed71zAFihEJmo6zkbHdvhA@mail.gmail.com>
Diego,
I agree with Ross here in from my experience with embedded systems the three best ways to strip your root
file system are by removing unneeded boot loader coe, removing unneeded kernel components and that of striping
your middle ware to smaller versions like Busybox and other similiar packages like elibc. Also running strip
after your debugging is done for the target can strip your code even further, there are cases of stripping large
programs like the kernel down from 20 megabytes to 2. Lastly, linking Busybox statically is great if you don't need
a reason to link it against a C library implementation as static versions of Busybox can easily be less then 10
megabytes from my reading and experience.
Regards Nick
On 14-11-08 01:03 PM, Diego Sueiro wrote:
> Take a look at poky-tiny distro:
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/distro/poky-tiny.conf
>
> As you are using BBB you can optimize u-boot code and remove some board
> detection steps.
>
> I noticed that MLO generated by u-boot 2014.07 mainline is too much faster
> than the old ones.
>
> Regards,
>
> --
> *dS
> Diego Sueiro
> sent from mobile.
> Em 08/11/2014 12:54, "Burton, Ross" <ross.burton@intel.com> escreveu:
>
>>
>> On 8 November 2014 14:23, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>
>>> I'm planning to just start excluding some of the packages in it ... I
>>> don't need sound, wireless, Bluetooth etc.
>>>
>>>
>> If you don't need sound, wifi, and bluetooth then remove the relevant
>> flags from DISTRO_FEATURES and they'll never be built.
>>
>> Ross
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>
>
>
prev parent reply other threads:[~2014-11-09 4:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 14:00 Build optimization question Dean
2014-11-08 14:23 ` Brian Hutchinson
2014-11-08 14:29 ` Brian Hutchinson
2014-11-08 14:53 ` Burton, Ross
2014-11-08 18:03 ` Diego Sueiro
2014-11-09 4:27 ` nick [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=545EED1B.5030203@gmail.com \
--to=xerofoify@gmail.com \
--cc=diego.sueiro@gmail.com \
--cc=ross.burton@intel.com \
--cc=yocto@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.