PTU5KAS/docs/format-changelog.rst

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.
Switch to separate config file version Use a separately incremented integer to track the configuration file format version. We start with 2 due to the change that 23c3a951f6e4 introduced. 1 is declared to be equivalent to the original '0.10'. The separate versioning has the advantage of being able to increment it already during the development cycle, and using it with config files that test/exploit the new format. Using an integer has the advantages of a) differentiating it clearly from the now independent kas version and b) simplifying the version parsing. We can now also remove the string type restriction. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> 2017-07-17 22:38:05 +02:00			`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`
docs/format-changelog.rst: Updated to include the recent changes This patch updated the 'docs/format-changelog.rst' file to include information about the configuration file version 3 and 4. Signed-off-by: Claudius Heine <ch@denx.de> 2017-10-16 10:44:11 +02:00
			`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
multiconfig: implement initial support This patch adds multiconfig support to kas by defining the "BBMULTICONFIG" variable in the "local.conf" file. Signed-off-by: Claudius Heine <ch@denx.de> 2017-11-07 17:20:17 +01:00
			`Version 5`
			`---------`

			`Changed behavior`
			`~~~~~~~~~~~~~~~~`

			- Using ``multiconfig:*`` targets adds appropriate ``BBMULTICONFIG`` entries to
			the ``local.conf`` automatically.
implementation of environment variable passthrough 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> 2017-11-23 14:15:51 +01:00
			`Version 6`
			`---------`

			`Added`
			`~~~~~`

			- ``env`` key now allows to pass custom environment variables to the bitbake
			`build process.`