| Summary: | bitbake-layers create-layer | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Robert Berger <pokylinux> |
| Component: | bitbake | Assignee: | Joshua Watt <JPEWhacker> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | JPEWhacker, poky.bs.watcher, poky.watcher, trevor.woerner, twoerner |
| Version: | unspecified | ||
| Target Milestone: | 2.6 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
Fix: http://lists.openembedded.org/pipermail/openembedded-core/2018-June/152413.html Test Cases: http://lists.openembedded.org/pipermail/openembedded-core/2018-June/152414.html At the ELCE devday it looks like this fix did not make it into the latest and greatest sumo branch. This is what we used at ELCE devday: commit d240b885f26e9b05c8db0364ab2ace9796709aad Author: Ola x Nilsson <ola.x.nilsson@axis.com> Date: Thu Oct 4 12:43:28 2018 +0200 Robert, Sorry about that. The target milestone was 2.6, so I don't think it was realized this needed to be backported. You could probably request a backport since it is on master now (although it's probably too late for the ELCE devday). @Joshua Watt - wow this was a quick reply. OK understood. I am working with your patch over Sumo and it works just fine for me. So, as my time permits, I might just create/push a backport (I guess you could guide me a bit, if necessary). Robert, Sure. The easiest thing to do is find the patch on the mailing list, then reply to it and ask it to be backported to sumo (CC'ing the stable branch maintainer, Armin Kuster <akuster808@gmail.com>). Alternatively, I *think* you could also send a new patch to the mailing list (also CC'ing Armin) with a subject like: [OE-core][sumo][PATCH] bitbake-bblayers/create: Fix layer name generation |
bitbake-layers create-layer --help NOTE: Starting bitbake server... usage: bitbake-layers create-layer [-h] [--priority PRIORITY] [--example-recipe-name EXAMPLERECIPE] [--example-recipe-version VERSION] layerdir Create a basic layer positional arguments: layerdir Layer directory to create optional arguments: -h, --help show this help message and exit --priority PRIORITY, -p PRIORITY Layer directory to create --example-recipe-name EXAMPLERECIPE, -e EXAMPLERECIPE Filename of the example recipe --example-recipe-version VERSION, -v VERSION Version number for the example recipe ---------------------------- + bitbake-layers create-layer --priority 6 --example-recipe-name example --example-recipe-version 0.1 ../meta-my-yocto-layer NOTE: Starting bitbake server... Add your new layer with 'bitbake-layers add-layer ../meta-my-yocto-layer' + tree ../meta-my-yocto-layer ../meta-my-yocto-layer ├── conf │ └── layer.conf ├── COPYING.MIT ├── README └── recipes-example └── example └── example_0.1.bb 3 directories, 4 files + cat ../meta-my-yocto-layer/conf/layer.conf # We have a conf and classes directory, add to BBPATH BBPATH .= ":${LAYERDIR}" # We have recipes-* directories, add to BBFILES BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \ ${LAYERDIR}/recipes-*/*/*.bbappend" BBFILE_COLLECTIONS += "../meta-my-yocto-layer" BBFILE_PATTERN_../meta-my-yocto-layer = "^${LAYERDIR}/" BBFILE_PRIORITY_../meta-my-yocto-layer = "6" LAYERDEPENDS_../meta-my-yocto-layer = "core" LAYERSERIES_COMPAT_../meta-my-yocto-layer = "sumo" ---------------------- is this valid? BBFILE_PATTERN_../meta-my-yocto-layer