34983c13ee
There is a subtle bug in SetupReposStep that occurs when: * One or more repositories are reported as "missing" in InitSetupRepos. * SetupReposStep checks out the missing repositories. * SetupReposStep updates the repo_dict with all repositories in the configuration, some of which may only be partially defined and/or not checked out. * SetupReposStep passes this new, incorrect list of checked out repositories to the include handler in the next pass. * The include handler attempts to include a file from a partially defined repository, likely resulting in a "File not found" error because it is assumed to be a local repository. To fix this, keep track of the repositories that have been checked out by only adding repositories that have been reported as "missing" to ctx.config.repo_dict Now that ctx.config.repo_dict only contains checked out repositories, it is necessary to check missing repo names against the config dict instead. Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> 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.