42e83cb7a3
Patches contain tailing white space in empty lines around a change, those are generally expected by git-apply and cause no issue. However in cases where a patch file is added, removed or modified in a patch, that patch would necessarily include `- ` or `+ ` lines, since they operate on patch files. Applying those patches with git-apply will cause git to print out warnings about tailing white spaces per default, but still applies the patch. Those warnings will be picked up by kas, and since they are coming from stderr, print them out as `ERRORS`. To solve this add `--whitespace=nowarn` as a parameter to the git-apply call to silence those warnings. In case of kas, it is to be expected that patches are added, removed or changed in meta layers, so those supposedly errors will cause confusion. Signed-off-by: Claudius Heine <ch@denx.de> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> |
||
---|---|---|
.github | ||
contrib | ||
docs | ||
image-tests | ||
kas | ||
scripts | ||
tests | ||
.dockerignore | ||
.flake8 | ||
.gitignore | ||
.readthedocs.yaml | ||
CHANGELOG.md | ||
container-entrypoint | ||
CONTRIBUTING.md | ||
Dockerfile | ||
Dockerfile.isar | ||
kas-container | ||
kas-docker | ||
LICENSE | ||
pyproject.toml | ||
README.rst | ||
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.