| Summary: | qwt fails in poky-lsb builds | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Other YP Layers | Reporter: | Ross Burton <ross.burton> |
| Component: | layers | Assignee: | Beth Flanagan <elizabeth.flanagan> |
| Status: | VERIFIED FIXED | QA Contact: | Mihail Stanciu <stanciux.mihail> |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | bluelightning, elizabeth.flanagan, joshuagloe, poky.bs.watcher, poky.watcher, stanciux.mihail |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 M3 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2016-01-25 15:11:08 UTC
I think building world with meta-qt4 enabled is probably not the right thing to be doing. If we have specific things to test in that layer, by all means let's build those explicitly, but seeing as it's now becoming the place where Qt4-using recipes from meta-oe are being placed, we don't need to be building everything in it anymore. Paul is right. We can accept whatever legacy qt4 apps people want to have into meta-qt4, but we're not obliged to keep those recipes up to standard and make them build without error. So you need to test strictly the things that are needed for LSB, which is, only qt4 itself. poky-lsb means enabling qt4. world builds are sensible. How are we going to exclude the bulk of meta-qt4 apart from the bits we want to build? It's almost like we need some sort of whitelist... This was resolved by adding poky-world-exclude.inc which excludes qwt from a world build: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b8fa9d36d81fadb817a797a6d41652e1fd3c283a Verified. |