| Summary: | implement "treat warnings as error" option | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Juro Bystricky <juro.bystricky> |
| Component: | core | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | meta.mr.watcher, meta.watcher, randy.macleod, sgw |
| Version: | 2.3 | ||
| Target Milestone: | 4.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Juro Bystricky
2017-04-12 16:15:53 UTC
The latter would be very hard... Fatal warnings as a bitbake option shouldn't be too difficult though. (In reply to comment #1) > The latter would be very hard... > > Fatal warnings as a bitbake option shouldn't be too difficult though. Ideally, if there is a warning, this should prevent writing of the corresponding build artefacts to the sstate. This way no new bitbake options are required and we should see the warning each time we repeat the build. Again, probably easier said than done. We have over the past 2 years, migrated many warnings to errors now so this issue has been addressed to some degree. |