<div style="font-family: Helvetica; font-size: 13px; ">Define EXCLUDE_FROM_WORLD = "1" in the recipe.<br></div>
<div><div><br></div><div>-- </div><div>Christopher Larson</div><div><br></div></div>
<p style="color: #A0A0A8;">On Thursday, April 12, 2012 at 5:52 PM, Robert Yang wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div><br></div><div>Thanks, is there a way to skip the pkg if I don't want to build it</div><div>when bitbake world, please?</div><div><br></div><div>// Robert</div><div><br></div><div>On 04/10/2012 10:15 PM, Chris Larson wrote:</div><blockquote type="cite"><div><div>On Tue, Apr 10, 2012 at 7:12 AM, Robert Yang<<a href="mailto:liezhi.yang@windriver.com">liezhi.yang@windriver.com</a>> wrote:</div><blockquote type="cite"><div><div>On 04/10/2012 09:58 PM, Chris Larson wrote:</div><blockquote type="cite"><div><div><br></div><div>On Tue, Apr 10, 2012 at 1:24 AM, Robert Yang<<a href="mailto:liezhi.yang@windriver.com">liezhi.yang@windriver.com</a>></div><div> wrote:</div><blockquote type="cite"><div><div><br></div><div>In the following code:</div><div><br></div><div>def buildWorldTargetList(self):</div><div>...</div><div> for f in self.status.possible_world:</div><div> terminal = True</div><div> pn = self.status.pkg_fn[f]</div><div><br></div><div> for p in pn_provides[pn]:</div><div> if p.startswith('virtual/'):</div><div> parselog.debug(2, "World build skipping %s due to %s</div><div>provider starting with virtual/", f, p)</div><div> terminal = False</div><div> break</div><div>...</div><div><br></div><div>Does it mean that if a recipe contains:</div><div><br></div><div>PROVIDES = "virtual/something"</div><div><br></div><div>Then it would not be built until a pkg depends on it? Why we design it in</div><div>this</div><div>way, please?</div></div></blockquote><div><br></div><div><br></div><div>The original intent with world was that when two recipes provided the</div><div>same thing, we'd still only want to build one of them, not both, as</div><div>building both can cause problems with stepping on one another in</div><div>sysroot, etc.</div></div></blockquote><div><br></div><div><br></div><div>Thanks for your reply, but it seems that it builts none currently.</div></div></blockquote><div><br></div><div>Fair point, I think in certain cases we also only wanted to build</div><div>things if they got pulled in via a dependency. For example, iirc</div><div>native and cross both exclude themselves from world via a variable set</div><div>in the classes. I don't recall if such was the case here, however.</div></div></blockquote></div></div></span>
</blockquote>
<div>
<br>
</div>