| Summary: |
Kernels with non-standard names don't provide virtual/kernel |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Ross Burton <ross.burton> |
| Component: |
kernel | Assignee: |
Bruce Ashfield <bruce.ashfield> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
randy.macleod, richard.purdie, tom.zanussi
|
| Version: |
0.0.0 | |
|
| Target Milestone: |
4.0 M2 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
We let kernel recipes name their packages something unique: kernel.bbclasss: KERNEL_PACKAGE_NAME ??= "kernel" But if the name isn't "kernel" then they don't provide virtual/kernel, so can't be really be used if all of the valid kernels have a name set: kernel.bbclasss: PROVIDES += "${@ "virtual/kernel" if (d.getVar("KERNEL_PACKAGE_NAME") == "kernel") else "" }" I believe that line should just be PROVIDES += "virtual/kernel".