summaryrefslogtreecommitdiffstats
path: root/scripts/lib/devtool/deploy.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-07 13:53:07 +0100
commit45f1409ce1d2bf084fe1acc18586aa389e27c355 (patch)
tree3526d76a6b594333b42e6facfb2333e8189fe3b7 /scripts/lib/devtool/deploy.py
parent2980a91e618eab5b8e91b8d4290f2df398ed24f5 (diff)
downloadpoky-45f1409ce1d2bf084fe1acc18586aa389e27c355.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 'scripts/lib/devtool/deploy.py')
0 files changed, 0 insertions, 0 deletions