SiegfriedSiegert/PTU5KAS
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

libcmds: Write more bblayers.conf boilerplate settings

Browse Source 
Irrespective of build system (OE / Yocto / Isar), they all have

    BBPATH = "${TOPDIR}"
    BBFILES ?= ""

in their bblayers_conf_header fragments. This could be dropped if kas
wrote those standard assignments already. So let's do that, weakly so
that those could still be overwritten via bblayers_conf_header.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
This commit is contained in:
Jan Kiszka 2021-10-11 08:10:29 +02:00
parent 95df3720e1
commit bfee47ebbc
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/format-changelog.rst
View File

@ -103,6 +103,8 @@ Changed behavior
- String item ``includes`` are now using repo-relative paths. File-relative is - String item ``includes`` are now using repo-relative paths. File-relative is
still supported by issues a deprecation warning. still supported by issues a deprecation warning.
- bblayers.conf is generated with ``BBPATH`` and ``BBFILES`` preset to common
defaults. Those can still be overwritten via ``bblayers_conf_headers``.
Added Added
~~~~~ ~~~~~

2
kas/libcmds.py
View File

@ -256,6 +256,8 @@ class WriteBBConfig(Command):
sorted(layer for repo in ctx.config.get_repos() sorted(layer for repo in ctx.config.get_repos()
for layer in repo.layers))) for layer in repo.layers)))
fds.write('"\n') fds.write('"\n')
fds.write('BBPATH ?= "${TOPDIR}"\n')
fds.write('BBFILES ??= ""\n')
def _write_local_conf(ctx): def _write_local_conf(ctx):
filename = ctx.build_dir + '/conf/local.conf' filename = ctx.build_dir + '/conf/local.conf'