| Summary: | bitbake-layers create-layer does create a new example layer with 'kirkstone' in LAYERSERIES_COMPAT | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Jan-Simon Moeller <dl9pf> |
| Component: | bitbake | Assignee: | Pavel Zhukov <pavel> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | dl9pf, pavel, poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 5.0 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Jan-Simon Moeller
2023-11-29 17:46:17 UTC
(In reply to Jan-Simon Moeller from comment #0) > bitbake-layers create-layer > does create a new example layer with 'kirkstone' in LAYERSERIES_COMPAT > > Reproduce: > > clone poky master > > run bitbake-layer create-layer ../meta-foo which bitbake/core version you're using at this step? looks like you're sourcing master later on which is the reason LAYERSERIES_COMPAT is different. > > source oe-init-build-env > bitbake-layer add-layer ../../meta-foo > > fails with compat error. $ git clone https://github.com/yoctoproject/poky.git Cloning into 'poky'... [...] $ . ./poky/oe-init-build-env bz15300 [...] $ bitbake-layers create-layer ../meta-foo NOTE: Starting bitbake server... Add your new layer with 'bitbake-layers add-layer ../meta-foo' $ bitbake-layers add-layer ../meta-foo NOTE: Starting bitbake server... $ grep COMPAT ../meta-foo/conf/layer.conf LAYERSERIES_COMPAT_meta-foo = "nanbield" Holidays and sick last week. Will get back after CES next week. We haven't heard from you for a while. I'm closing this bug based on previous comment I made. Please make sure you're sourcing appropriate branch prior creating the layer. Feel free to reopen this report if the issue still exists. |