Jan Kiszka 7248d5e1bb Fix termination steps
Another, hopefully better attempt: Ignore the TERM signal in the sending
process so that we can properly clean up all the futures before actually
closing. This also avoids a "Terminated" message even on regular kas
endings.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-06-29 09:09:50 +02:00
2017-06-29 09:09:50 +02:00
2017-06-26 09:29:07 +02:00
2017-06-28 15:12:15 +02:00
2017-06-14 15:21:19 +02:00
2017-06-14 15:21:19 +02:00
2017-06-29 09:05:02 +02:00
2017-06-14 15:21:19 +02:00
2017-06-14 15:21:19 +02:00
2017-06-23 08:36:48 +02:00

Setup tool for bitbake based projects

Branch Build Status
master Build Status
next Build Status

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

Documentation

Description
Languages
Python 85%
Shell 12.9%
Dockerfile 2.1%