diff options
author | Yoann Congal <yoann.congal@smile.fr> | 2025-10-02 12:09:27 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-10-04 11:16:43 +0100 |
commit | 540bf592be0be3834a9e55d92263b1bbdaa25d11 (patch) | |
tree | 43a477f650451bd778bbc1283b043a8604abc6db /meta/lib/patchtest/patchtest_parser.py | |
parent | f8f8df95bb39a057d464864385a9ad7b009606f7 (diff) | |
download | poky-540bf592be0be3834a9e55d92263b1bbdaa25d11.tar.gz |
bitbake: bitbake-setup: allow using {THISDIR}/my-layer
This implement the ability to use "{THISDIR}/my-layer" in the
"bb-layers" list. "{THISDIR}" is remplaced by the directory containing
the configuration file.
In small projects, we try to keep the setup a simple as possible: a
single git repo containing both the build confguration (e.g.
a bitbake-setup configuration file) and the meta layer with project
recipes/machine/distro.
This change allows this kind of setup:
├── meta-my-project/ # the project layer
└── my-project.conf.json # the bb-setup configuration file
by writing, in my-project.conf.json:
"bitbake-setup": {
"configurations": [{
"bb-layers": [
"{THISDIR}/meta-my-project"
Note: in this case meta-my-project is not present as a "source", so, not
handled by bb-setup update/status. It is expected of the user to handle
this on their own (is our case, a simple git workflow).
(Bitbake rev: 61fbdeb358979bb13c9e50d807f43e554497dc9c)
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/patchtest/patchtest_parser.py')
0 files changed, 0 insertions, 0 deletions