From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qw0-f48.google.com (mail-qw0-f48.google.com [209.85.216.48]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D9F40E0123F for ; Tue, 10 Jan 2012 07:02:17 -0800 (PST) Authentication-Results: yocto-www.yoctoproject.org; dkim=pass (1024-bit key; insecure key) header.i=@gmail.com; x-dkim-adsp=none (insecure policy) Received: by qadc16 with SMTP id c16so3371917qad.14 for ; Tue, 10 Jan 2012 07:02:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=N7R/AJqmbGouWtPYdt3OEV/lg8sjwQ2dQfOEHbpG3Zo=; b=XdizHbekgFc6eVXu09Oba92cq4xrg/FLYQrueiew1bOzoIKt8C1ujWp9c50LbPTBWI nqx2K9MjBidYexDJgcfQjH5zgMI1MDj+BtY95AS3KdJT8PcRI2zkaIiHw6eRCfeNe+N0 eYdn+31BUHUHpZ8NP7SC7A+3v9ZdSsM3gIXoE= Received: by 10.224.17.135 with SMTP id s7mr25771017qaa.65.1326207736908; Tue, 10 Jan 2012 07:02:16 -0800 (PST) Received: from [10.0.1.39] (nc-184-3-54-63.dhcp.embarqhsd.net. [184.3.54.63]) by mx.google.com with ESMTPS id q14sm149898799qap.4.2012.01.10.07.02.15 (version=SSLv3 cipher=OTHER); Tue, 10 Jan 2012 07:02:16 -0800 (PST) Message-ID: <4F0C52F5.4010006@gmail.com> Date: Tue, 10 Jan 2012 10:02:13 -0500 From: Jim Abernathy User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: yocto@yoctoproject.org References: <8B3C6E23-C3B9-4CEF-A1E0-2B91F8D17EFE@gmail.com> <2F4E813B930D429F95E9E2DCFB2C36A2@gmail.com> <4F0C4FBF.6080100@gmail.com> <4F0C51EC.1030401@mlbassoc.com> In-Reply-To: <4F0C51EC.1030401@mlbassoc.com> Subject: Re: understanding what's in an image X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2012 15:02:18 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 01/10/2012 09:57 AM, Gary Thomas wrote: > On 2012-01-10 07:48, Jim Abernathy wrote: >> On 01/09/2012 09:07 PM, Christopher Larson wrote: >>> Read layer.conf in each layer. See the BBFILES variable. >>> -- >>> Christopher Larson >>> >>> On Monday, January 9, 2012 at 5:51 PM, James Abernathy wrote: >>> >>>> I'm trying to understand how bitbake parses the poky directory tree >>>> a little better. >>>> >>>> The best I can figure all .bb files are NOT included. Just some of >>>> them are. I'm guessing that the .bb in the meta/recipe-sato named >>>> core-image-sato.bb is the one that is used >>>> to start the parsing if bitbake core-image-sato is executed. >>>> I originally thought all subdirectories of a path included in >>>> BBLAYER were parsed looking for .bb files, but now I know that is >>>> not true, but not sure why. >>>> >>>> For example, it does not appear that webkit is included in the >>>> core-image-sato even though the recipe-sato directory includes the >>>> webkit subdirectory with it's recipe. What >>>> would be the proper way of adding the webkit to core-image-sato?? >>>> >>>> Jim A >>>> >>>> _______________________________________________ >>>> yocto mailing list >>>> yocto@yoctoproject.org >>>> https://lists.yoctoproject.org/listinfo/yocto >>> >> the layer.conf in meta/conf includes and covers all .bb files under >> it like receipe-sato, which includes web-webkit. So does this say >> that the web-webkit get's built by bitbake, >> but the images does not contain web-webkit until you put in the >> IMAGE_INSTALL += "web-webit"??? > > No, only packages which are needed to satisfy the needs of > the given image are built. So, if your image does not include > web-webkit, it won't be built even though there is a recipe > for it. > > When building an image, bitbake looks at the image recipe and > figures out what packages are needed (these are listed explicitly). > Then any additional packages which are needed (DEPENDS, RDEPENDS, etc) > will be added to the list. This process continues until all > dependencies are met, yielding the final package set. Out of > the 1000 or so possible recipes, you may end up only building > a few hundred and many of these are support - i.e. only used > for the build process itself. > This makes sense now, thanks. I did this via hob this morning and it become more obvious because hob approaches this process as all about the package. Jim A