Configuration Format Changes¶
Version 2¶
Changed¶
- Configuration file versions are now integers
Fixed¶
- Including files from repos that are not defined in the current file
Version 5¶
Changed behavior¶
- Using
multiconfig:*
targets adds appropriateBBMULTICONFIG
entries to thelocal.conf
automatically.
Version 6¶
Added¶
env
key now allows to pass custom environment variables to the bitbake build process.
Version 9¶
Added¶
defaults
key can now be used to set a default value for the repository propertyrefspec
and the repository patch propertyrepo
. These default values will be used if the appropriate properties are not defined for a given repository or patch.
Version 11¶
Changed behavior¶
- String item
includes
are now using repo-relative paths. File-relative is still supported by issues a deprecation warning. - bblayers.conf is generated with
BBPATH
andBBFILES
preset to common defaults. Those can still be overwritten viabblayers_conf_headers
.
Added¶
menu_configuration
key stores the selections done viakas menu
in a configuration file. It is only evaluated by that plugin.
Version 12¶
Added¶
- For repositories,
url
andpath
can now be overridden with a null-value to switch between version-controlled repositories and unversioned local folders.
Version 13¶
Added¶
- Variables used in the
env
section can now be assigned ‘None’ as value. In this case the variables are only exported to the bb env whitelist.
Version 14¶
Added¶
- The keys
commit
andbranch
are introduced as replacement ofrefspec
inrepos
anddefaults
.refspec
is now deprecated and will eventually be removed. - The
overrides
top-level entry can be used to pin floating repo branches. _source_dir
top-level entry is auto-generated when using the menu plugin and provides the path to the top repo at time of invoking the plugin._source_dir_host
top-level entry is auto-generated by kas-container to track the source path outside of the container.