4795c21fb6
These additional test cases check if the env section can: - export variables with their default value - add variables with 'None' assigned only to BB_ENV_PASSTHROUGH_ADDITIONS or to the deprecated BB_ENV_EXTRAWHITE - bitbake: make sure that variables actually make it into bitbake The BB_ENV_EXTRAWHITE variable is still present, so a test case has also been added for this. Signed-off-by: Benedikt Niedermayr <benedikt.niedermayr@siemens.com> [Jan: ensure python 3.5 compatibility, adjust copyright header] Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Setup tool for bitbake based projects ===================================== +--------------------+ | Build Status | +====================+ | |workflow-master|_ | +--------------------+ | |workflow-next|_ | +--------------------+ .. |workflow-master| image:: https://github.com/siemens/kas/workflows/master/badge.svg .. _workflow-master: https://github.com/siemens/kas/actions?query=workflow%3Amaster .. |workflow-next| image:: https://github.com/siemens/kas/workflows/next/badge.svg .. _workflow-next: https://github.com/siemens/kas/actions?query=workflow%3Anext This tool provides an easy mechanism to setup bitbake based projects. The OpenEmbedded tooling support starts at step 2 with bitbake. The downloading of sources and then configuration has to be done by hand. Usually, this is explained in a README. Instead kas is using a project configuration file and does the download and configuration phase. Key features provided by the build tool: - clone and checkout bitbake layers - create default bitbake settings (machine, arch, ...) - launch minimal build environment, reducing risk of host contamination - initiate bitbake build process See the `kas documentation <https://kas.readthedocs.io>`_ for further details.