| Summary: | bitbake -g can't figure out non-existed packages | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Robert Yang <liezhi.yang> |
| Component: | bitbake | Assignee: | Robert Yang <liezhi.yang> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | mark.hatle, poky.bs.watcher, poky.watcher, randy.macleod, richard.purdie, ross.burton, sgw |
| Version: | 1.6 | ||
| Target Milestone: | 2.4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Robert Yang
2013-11-14 09:12:40 UTC
The problem is that the dhcp recipe has dhcp in PACKAGES, but it is empty so doesn't actually get generated. Bitbake can't know this, so it is doing the right thing. (a proper fix would be to stop the dhcp recipe from claiming it produces a dhcp package) Hm, no, sorry didn't read the report correctly. If you do PACKAGES_remove=$PN then bitbake still tries to build an image. cache.py, CoreRecipeInfo constructor:
if not self.pn in self.packages:
self.packages.append(self.pn)
if PN isn't in the PACKAGES list, add PN.
Simply commenting out that line breaks the cache as native packages don't have PACKAGES. Maybe native should just set PACKAGES=PN?
Patch on the list Fixed in bitbake df31a88786ce5bd7708ff14e1379dc2a58a8c0cf. |