From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from tritech.se ([91.191.137.61]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1Qh1Yk-0001BK-GE for openembedded-devel@lists.openembedded.org; Wed, 13 Jul 2011 17:41:10 +0200 Received: from post.tritech.se (post.tritech.se [10.75.60.100]) by tritech.se (8.14.3/8.14.3) with ESMTP id p6DFb6E2014923 for ; Wed, 13 Jul 2011 17:37:11 +0200 Received: from POST.tritech.se ([fe80::b4fc:968e:bbef:54cb]) by post.tritech.se ([fe80::b4fc:968e:bbef:54cb%11]) with mapi id 14.01.0270.001; Wed, 13 Jul 2011 17:37:06 +0200 From: =?iso-8859-1?Q?Mats_K=E4rrman?= To: "openembedded-devel@lists.openembedded.org" Thread-Topic: [oe] Unwanted dependency on X from ppp Thread-Index: AcxBVadKX3oznpENRgmgOmmUfA9rmgAAVVyAAAY+8nE= Date: Wed, 13 Jul 2011 15:37:05 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US, sv-SE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [194.132.137.34] MIME-Version: 1.0 Subject: Re: Unwanted dependency on X from ppp X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2011 15:41:10 -0000 Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you Bob!=0A= =0A= You're my hero, honestly!=0A= =0A= The "clean build" time concerns me though. I will need bluez components,=0A= but not gstreamer so I guess I'll set out to find a neat way to override=0A= the default bluez recipe and get rid of that dependency.=0A= =0A= // Mats=0A= =0A= ________________________________________ =0A= From: openembedded-devel-bounces@lists.openembedded.org [openembedded-devel= -bounces@lists.openembedded.org] on behalf of Bob Foerster [robert@erafx.co= m]=0A= Sent: Wednesday, July 13, 2011 4:18 PM=0A= To: openembedded-devel@lists.openembedded.org=0A= Subject: Re: [oe] Unwanted dependency on X from ppp=0A= =0A= Hi Mats,=0A= =0A= On Wed, Jul 13, 2011 at 8:16 AM, Mats K=E4rrman wr= ote:=0A= =0A= > Hi Everyone!=0A= >=0A= > I'm building a small "headless" embedded system with OE and the Angstrom= =0A= > distro. A normal rootfs build consists of about 1500 tasks. Everything fi= ne=0A= > so far.=0A= >=0A= > Now I wanted to include the ppp daemon in my build and thus just added=0A= > "ppp" to IMAGE_INSTALL. Suddenly the rootfs build is about 4000 tasks and= a=0A= > lot of X/display related stuff is downloaded and built. I fail to see the= =0A= > connection.=0A= >=0A= =0A= Are the X/display items you're concerned about actually making it into the= =0A= final image, or just being built? If they are ending up in the image, then= =0A= it will take some investigation as to why that's happening. If they're just= =0A= being built there is probably not much you can do, but the following may=0A= help shed some light as to why they are built.=0A= =0A= To understand why adding ppp pulls in various X/display packages, keep in= =0A= mind that what is downloaded and built does not directly correlate to what= =0A= ends up in the image. Often, recipes may provide several packages which=0A= have a broad set of build time dependencies, but these don't all necessaril= y=0A= end up in the image.=0A= =0A= For tracking down dependencies, you can fire up the dependency explorer gui= =0A= for bitbake:=0A= bitbake -g -u depexp ppp=0A= =0A= Doing this and following the trail, one sees:=0A= ppp -> libpcap -> bluez-libs (here, bluez4 is selected as provider for=0A= bluez-libs) -> gst-plugins-base -> gtk+ -> libx*=0A= =0A= Given this dependency chain, we start to see why building ppp causes variou= s=0A= gtk+ and X packages to be built. The bluez4 recipe provides a package=0A= gst-plugin-bluez, causing a build time dependency on gst-plugins-base.=0A= gst-plugins-base depends on many things, including gtk+. As a result of= =0A= these dependencies, many packages end up being built. The shlibs code in O= E=0A= automatically detects the run time libs required for a given package and=0A= appropriately associates run time dependencies on them. As such, unless on= e=0A= adds gst-plugin-bluez to IMAGE_INSTALL, I wouldn't expect the various gtk+,= =0A= libx*, etc packages to make it into the final image. If they are, then=0A= there is another dependency that is pulling them into the image and needs= =0A= explored. For a little bit more background on build vs run time=0A= dependencies, see [1].=0A= =0A= Hope that helps clarify a bit.=0A= Bob=0A= =0A= [1]=0A= http://dominion.thruhere.net/koen/cms/reducing-the-size-of-your-angstrom-ro= otfs-without-changing-the-buildsystem=0A= =0A= =0A= =0A= > I'm afraid I'm not using the latest trunk or release of OE but any=0A= > suggestions or directions on how to find/eliminate the cause of the probl= em=0A= > would be greatly appreciated!=0A= >=0A= > Best Regards,=0A= > Mats=0A= >=0A= > _______________________________________________=0A= > Openembedded-devel mailing list=0A= > Openembedded-devel@lists.openembedded.org=0A= > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel=0A= >=0A= _______________________________________________=0A= Openembedded-devel mailing list=0A= Openembedded-devel@lists.openembedded.org=0A= http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel=0A=