dd04836896
This seems to be the cleanest and simplest way of properly terminating kas while one or more sub-processes are running: just ignore the signal. The sub-processes will get it as well, and they will terminate themselves properly. kas will get an error then and shut down. Problem solved. Forwarding the signal didn't work reliably anyway because we couldn't count on kas being a process group leader in all cases. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Setup tool for bitbake based projects
| Branch | Build Status |
|---|---|
master |
 |
next |
 |
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.
Currently supported Yocto versions:
- 2.1 (Krogoth)
- 2.2 (Morty)
Older or newer versions may work as well but haven't been tested intensively.
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