503cf183b1
This patch introduces new and improved ways to overwrite kas-container variables that specify which image should be used. `KAS_CONTAINER_IMAGE_PREFIX`: can be used to overwrite image sources. For instance if podman is used, the default value `docker://` is used as a prefix. But it still allows to overwrite it, by setting a custom variable. `KAS_CONTAINER_IMAGE_PATH`: can be used to customize the image source path. `KAS_CONTAINER_IMAGE_NAME`: can be set to change the container image name. For instance if `--isar` is used, the default value is `kas-isar`, as with `KAS_CONTAINER_IMAGE_PREFIX` this default value can still be overwritten by setting a custom value. And last `KAS_IMAGE_VERSION`: It was possible to overwrite this value before this patch and its still possible. The default value is the current release version. Setting it for instance to `latest`, would allow to used the most recent version of the image. Signed-off-by: Claudius Heine <ch@denx.de> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| kas | ||
| scripts | ||
| tests | ||
| .dockerignore | ||
| .flake8 | ||
| .gitignore | ||
| CHANGELOG.md | ||
| container-entrypoint | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| Dockerfile.isar | ||
| kas-container | ||
| kas-docker | ||
| LICENSE | ||
| README.rst | ||
| requirements_rtd.txt | ||
| run-kas | ||
| setup.py | ||
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.