6e82e0d12d
There are situation that the user have a local customized container images with tools installed that are not provided in the default kas container. - For a local container the user can tag it and use the existing variables: docker tag local-container my/container:1.0 export KAS_CONTAINER_IMAGE_PATH=my export KAS_CONTAINER_IMAGE_NAME=container export KAS_IMAGE_VERSION=1.0 - This patch improve the user interface by allowing to set a custom image with just a single environment variable. export KAS_CONTAINER_IMAGE=local-container Signed-off-by: Jose Quaresma <quaresma.jose@gmail.com> 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.