Return-Path: Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B2A67E014B4 for ; Mon, 27 May 2013 07:56:45 -0700 (PDT) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Ugyqk-0000qx-SN for yocto@yoctoproject.org; Mon, 27 May 2013 16:56:40 +0200 Received: from 212.50.246.123 ([212.50.246.123]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 May 2013 16:56:38 +0200 Received: from jackrubby2010 by 212.50.246.123 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 May 2013 16:56:38 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: yocto@yoctoproject.org From: Jack Date: Mon, 27 May 2013 14:56:18 +0000 (UTC) Message-ID: References: <5394411.Nd6qyTtVKA@helios> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 212.50.246.123 (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0) Subject: Re: How can I remove packages from rootfs file ? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 14:56:46 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks a lot Paul. Paul Eggleton writes: > > On Saturday 25 May 2013 13:58:46 Jack wrote: > > I maked a fsl-image-minaml rootfs file and customized it with adding > > particular packages. For example, I added > > IMAGE_INSTALL_append_pn-fsl-image-minimal = " task-core-ssh-openssh > > task-core-nfs-server" in local.conf file. The problem is that, the rootfs > > file has 6-7 MB capacity but this capacity of file is very high and not > > acceptable to me. So how can I remove some packages from rootfs file that I > > do not want ? > > There are several different aspects to answering this question. > > The list of packages to be installed is composed of several things - the list > of packages specified in IMAGE_INSTALL, packages brought in by IMAGE_FEATURES, > and packages brought in to satisfy dependencies of either of the first two. > > One way to analyse the contents of your image is to enable buildhistory [1] > which gives you the full list of installed packages, installed packages by > size, as well as graphs (.dot) that will show you the dependency relationships > between the packages. These dot graphs can be viewed by converting them to > images using the "dot" command (from graphviz) or using a viewer such as xdot > [2]. I enabled buildhistory by adding INHERIT += "buildhistory" and BUILDHISTORY_COMMIT = "1" to local.conf file. But I got this error : | error: Failed dependencies: | libcrypt.so.1(GLIBC_2.0) is needed by inetutils-1.8-r0.ppce500v2 . . . . How can I solve this error ? > > Once you've analysed things at this level, you may find there are dependency > relationships that can't easily be broken, or some packages that are overly > large. At this point you will need to start looking at changing the build > configuraton of the packages in question - disabling optional functionalty, > removing optional dependencies etc. (usually this would be done by changing > DISTRO_FEATURES, modifying the kernel configuration, changing PACKAGECONFIG > options for individual recipes, or if those aren't available modifying > EXTRA_OECONF). How far you want to go with this depends on how much you want > to optimise the size of your image. > > If you do find you need to go down the latter path, I'd recommend checking out > Darren Hart's presentation "Tuning Embedded Linux - When Less is More" [3]. I changed DISTRO_FEATURES in local.conf to DISTRO_FEATURE = "busybox" but it didn't compile. > > > For example, remove packages like ar, arping, basename, telnet, beep, ..... > > Note that whilst some of these may be from packages you can remove, many of > them may be functionality provided by busybox, i.e. where the command is just > a symlink to the busybox binary. You can modify the busybox build-time > configuration to disable these, but bear in mind that disabling them > usually only saves you a few kB. For some applications that may be a useful > saving, of course. > > HTH. > > Cheers, > Paul > > [1] http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality > > [2] https://github.com/jrfonseca/xdot.py > > [3] Slides: http://elinux.org/images/2/2b/Elce11_hart.pdf > Video: http://www.youtube.com/watch?v=WHLvI8j31vk > Finally, I found that one way to customize an image is hob. I remove some packages with hob and the size of my root filesystem decreased. The type of output file that generated is .rootfs.ext2.gz but I need .rootfs.ext2.gz.u-boot type. How can I have .rootfs.ext2.gz.u-boot type with hob? Is it possible convert .rootfs.ext2.gz to .rootfs.ext2.gz.u-boot?