Claudius Heine
95015045db
With this its possible to create custom environment variables within the kas
configuration file, that are passed through to the build environment:
env:
VARIABLE_NAME: "default variable value"
Those variables can be overwritten by variables of the environment kas is
started in:
$ VARIABLE_NAME="overwritten variable value" kas shell ...
Those variables are also added to the 'BB_ENV_EXTRAWHITE' variable list to make
them available to bitbake.
This is useful for instance storing sensitive information, that should not be
part of the configuration files or bitbake recipes.
Signed-off-by: Claudius Heine <ch@denx.de>
60 lines
832 B
ReStructuredText
60 lines
832 B
ReStructuredText
Configuration Format Changes
|
|
============================
|
|
|
|
Version 1 (Alias '0.10')
|
|
------------------------
|
|
|
|
Added
|
|
~~~~~
|
|
|
|
- Include mechanism
|
|
- Version check
|
|
|
|
|
|
Version 2
|
|
---------
|
|
|
|
Changed
|
|
~~~~~~~
|
|
|
|
- Configuration file versions are now integers
|
|
|
|
Fixed
|
|
~~~~~
|
|
|
|
- Including files from repos that are not defined in the current file
|
|
|
|
Version 3
|
|
---------
|
|
|
|
Added
|
|
~~~~~
|
|
|
|
- ``Task`` key that allows to specify which task to run (``bitbake -c``)
|
|
|
|
Version 4
|
|
---------
|
|
|
|
Added
|
|
~~~~~
|
|
|
|
- ``Target`` key now allows to be a list of target names
|
|
|
|
Version 5
|
|
---------
|
|
|
|
Changed behavior
|
|
~~~~~~~~~~~~~~~~
|
|
|
|
- Using ``multiconfig:*`` targets adds appropriate ``BBMULTICONFIG`` entries to
|
|
the ``local.conf`` automatically.
|
|
|
|
Version 6
|
|
---------
|
|
|
|
Added
|
|
~~~~~
|
|
|
|
- ``env`` key now allows to pass custom environment variables to the bitbake
|
|
build process.
|