| Summary: |
bitbake errors must have unique ids to make them easily greppable in the source |
| Product: |
[Build System, Metadata & Runtime] BitBake
|
Reporter: |
Alexandru Damian <alexandru.damian> |
| Component: |
bitbake | Assignee: |
Unassigned <unassigned> |
| Status: |
RESOLVED
WONTFIX
|
QA Contact: |
|
| Severity: |
enhancement
|
|
|
| Priority: |
Low
|
CC: |
bluelightning, poky.bs.watcher, poky.watcher, richard.purdie
|
| Version: |
1.8 | |
|
| Target Milestone: |
Future | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
Yes (doc changes required)
|
|---|
Bitbake error must be prefixed with a unique ID, for each error, in the form "BBxyyyy" where "x" is a error severity indicator ("E", "W", "I" or "D" for Error, Warning, Info or Debug) and "yyyy" is a numeric ID starting with 0001. E.g. instead of: "Only one copy of bitbake should be run against a build directory" bitbake output should be "BBE0001: Only one copy of bitbake should be run against a build directory" Having unique textual IDs for errors make grepping through the source a lot easier, to allow for easy reference of code without having to hardcode locations. E.g. a web interface could display relevant sections of code based on the error unique id by grepping through the source.