2f60b982a7
The leakage of grub artifacts from the building Debian version and the usage its grub tools was fixed in Isar 0.6 already. No one is expected to use that old version with latest kas containers, and the presence of these packages also collide with providing non-x86 versions. 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.