summaryrefslogtreecommitdiffstats
path: root/meta/lib/patchtest/repo.py
diff options
context:
space:
mode:
authorYoann Congal <yoann.congal@smile.fr>2025-10-02 12:09:27 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-10-09 22:05:17 +0100
commit3717776c6401d637175f5a0a70db0c916192f309 (patch)
treef3d992014ecf43f0e0d1463ccd70f66e277d380d /meta/lib/patchtest/repo.py
parent4a30a1fac23442d0cb8829f083a749b932eb9ce6 (diff)
downloadpoky-3717776c6401d637175f5a0a70db0c916192f309.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: 7826a4d43cbee19bd6510f3c940f379c02f11345) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/patchtest/repo.py')
0 files changed, 0 insertions, 0 deletions