Go to file
Jan Kiszka 2a618686f1 Switch to separate config file version
Use a separately incremented integer to track the configuration file
format version. We start with 2 due to the change that 23c3a951f6
introduced. 1 is declared to be equivalent to the original '0.10'.

The separate versioning has the advantage of being able to increment it
already during the development cycle, and using it with config files
that test/exploit the new format.

Using an integer has the advantages of a) differentiating it clearly
from the now independent kas version and b) simplifying the version
parsing. We can now also remove the string type restriction.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-07-20 15:31:23 +02:00
docs Switch to separate config file version 2017-07-20 15:31:23 +02:00
kas Switch to separate config file version 2017-07-20 15:31:23 +02:00
scripts Added initial sphinx documentation 2017-06-28 15:12:15 +02:00
tests Switch to separate config file version 2017-07-20 15:31:23 +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 travis: Push next builds under separate tag 2017-07-12 10:22:15 +02:00
CHANGELOG.md Release 0.10.0 2017-07-10 12:27:26 +02:00
CONTRIBUTING.md Initial public release 2017-06-14 15:21:19 +02:00
docker-entrypoint docker: Warn about broken host setup based on aufs 2017-07-08 16:21:11 +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.rst README: Convert to structured text 2017-07-20 15:29:12 +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 README: Convert to structured text 2017-07-20 15:29:12 +02:00

Setup tool for bitbake based projects
=====================================

+------------+------------------+
|   Branch   |   Build Status   |
+============+==================+
| ``master`` | |travis-master|_ |
+------------+------------------+
| ``next``   | |travis-next|_   |
+------------+------------------+

.. |travis-master| image:: https://travis-ci.org/siemens/kas.svg?branch=master
.. _travis-master: https://travis-ci.org/siemens/kas/branches
.. |travis-next| image:: https://travis-ci.org/siemens/kas.svg?branch=next
.. _travis-next: https://travis-ci.org/siemens/kas/branches

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.