Go to file
Jan Kiszka dd04836896 Ignore SIGINT/TERM at kas level, let sub-processes handle it
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>
2017-07-06 09:05:52 +02:00
docs docs: added description of DL_DIR, SSTATE_DIR, TMPDIR env variables 2017-06-29 08:53:17 +02:00
kas Ignore SIGINT/TERM at kas level, let sub-processes handle it 2017-07-06 09:05:52 +02:00
scripts Added initial sphinx documentation 2017-06-28 15:12:15 +02:00
.dockerignore add dockerignore 2017-06-26 09:29:07 +02:00
.gitignore Expanded and documented .gitignore 2017-06-28 15:12:15 +02:00
.pylintrc Fixed issues that occured with pylint 1.7.2 2017-06-28 15:10:14 +02:00
.travis.yml Add Dockerfile for Isar image builder 2017-06-29 09:09:08 +02:00
CHANGELOG.md Initial public release 2017-06-14 15:21:19 +02:00
CONTRIBUTING.md Initial public release 2017-06-14 15:21:19 +02:00
docker-entrypoint docker: Rename USER_ID variable 2017-06-19 10:47:02 +02:00
Dockerfile add yocto 2.1 in comment 2017-06-29 09:05:02 +02:00
Dockerfile.isar Add Dockerfile for Isar image builder 2017-06-29 09:09:08 +02:00
LICENSE Initial public release 2017-06-14 15:21:19 +02:00
README.md README.md: Replaced documentation links to a readthedocs link 2017-06-29 08:49:03 +02:00
requirements_rtd.txt Made project buildable with rtd 2017-06-28 15:12:15 +02:00
run-kas Initial public release 2017-06-14 15:21:19 +02:00
setup.py Add install_requires in setup.py 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