Re: [yocto] Build optimization question
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" escreveu: > >> >> On 8 November 2014 14:23, Brian Hutchinson 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 >> >> > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build optimization question
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" escreveu: > > On 8 November 2014 14:23, Brian Hutchinson 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 > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build optimization question
On 8 November 2014 14:23, Brian Hutchinson 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
Re: [yocto] Build optimization question
On Nov 8, 2014 9:23 AM, "Brian Hutchinson" wrote: > > > On Nov 8, 2014 9:02 AM, "Dean" wrote: > > > > So I am using core-image-minimal and trying to shrink things as much as possible for boot speed. I wrap the bitbake command in some other commands to basically extract the image and then attach it to a kernel as a ramdisk. So the size of the image is critical to boot speed. > > > > In some of my custom packages I have used -Os in the gcc command line. > > Is there a way to set this globally for all the packages built into the image? > > > > Any other hints or tips to reduce the size of the build? Or potential changes to u-boot to make it load faster? This is running on a beaglebone black. > > > > > > Thanks, > > Dean > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > ... I've been noticing over the last few releases that core - image - minimal isn't so minimal anymore. Its been picking up weight as it ages (like me). > > I'm planning to just start excluding some of the packages in it ... I don't need sound, wireless, Bluetooth etc. > > Regards, > > Brian ... going from memory about my last dizzy build, /use/share was 35M. I've been using the rootfs tar to build my image and exclude some of this stuff but I need to look into ways to tame this kind of thing with recipes etc. Regards, Brian -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build optimization question
On Nov 8, 2014 9:02 AM, "Dean" wrote: > > So I am using core-image-minimal and trying to shrink things as much as possible for boot speed. I wrap the bitbake command in some other commands to basically extract the image and then attach it to a kernel as a ramdisk. So the size of the image is critical to boot speed. > > In some of my custom packages I have used -Os in the gcc command line. > Is there a way to set this globally for all the packages built into the image? > > Any other hints or tips to reduce the size of the build? Or potential changes to u-boot to make it load faster? This is running on a beaglebone black. > > > Thanks, > Dean > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ... I've been noticing over the last few releases that core - image - minimal isn't so minimal anymore. Its been picking up weight as it ages (like me). I'm planning to just start excluding some of the packages in it ... I don't need sound, wireless, Bluetooth etc. Regards, Brian -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build optimization question
So I am using core-image-minimal and trying to shrink things as much as possible for boot speed. I wrap the bitbake command in some other commands to basically extract the image and then attach it to a kernel as a ramdisk. So the size of the image is critical to boot speed. In some of my custom packages I have used -Os in the gcc command line. Is there a way to set this globally for all the packages built into the image? Any other hints or tips to reduce the size of the build? Or potential changes to u-boot to make it load faster? This is running on a beaglebone black. Thanks, Dean -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
