From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.windriver.com ([147.11.1.11]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SHbwz-0004w9-H8 for bitbake-devel@lists.openembedded.org; Tue, 10 Apr 2012 16:21:41 +0200 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id q3AECJVd015165 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Apr 2012 07:12:19 -0700 (PDT) Received: from [128.224.162.196] (128.224.162.196) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Tue, 10 Apr 2012 07:12:19 -0700 Message-ID: <4F843FC1.1080309@windriver.com> Date: Tue, 10 Apr 2012 22:12:17 +0800 From: Robert Yang User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120310 Thunderbird/11.0 MIME-Version: 1.0 To: Chris Larson References: <4F83EE3C.8040904@windriver.com> In-Reply-To: Cc: bitbake-devel@lists.openembedded.org Subject: Re: questions about bitbake world X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 14:21:41 -0000 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit On 04/10/2012 09:58 PM, Chris Larson wrote: > On Tue, Apr 10, 2012 at 1:24 AM, Robert Yang wrote: >> In the following code: >> >> def buildWorldTargetList(self): >> ... >> for f in self.status.possible_world: >> terminal = True >> pn = self.status.pkg_fn[f] >> >> for p in pn_provides[pn]: >> if p.startswith('virtual/'): >> parselog.debug(2, "World build skipping %s due to %s >> provider starting with virtual/", f, p) >> terminal = False >> break >> ... >> >> Does it mean that if a recipe contains: >> >> PROVIDES = "virtual/something" >> >> Then it would not be built until a pkg depends on it? Why we design it in >> this >> way, please? > > The original intent with world was that when two recipes provided the > same thing, we'd still only want to build one of them, not both, as > building both can cause problems with stepping on one another in > sysroot, etc. Thanks for your reply, but it seems that it builts none currently. // Robert