summaryrefslogtreecommitdiffstats
path: root/scripts/cve-json-to-text.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-03 17:51:38 +0100
commit9d75083a8ed21501b19b4fd0cc970d1361dd4a0c (patch)
tree129a57772a21a6995f308343945cb6b800189091 /scripts/cve-json-to-text.py
parent57616e76b44601ce64582777fa7249d3a4ac6c5e (diff)
downloadpoky-9d75083a8ed21501b19b4fd0cc970d1361dd4a0c.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/cve-json-to-text.py')
0 files changed, 0 insertions, 0 deletions