Go to file
Claudius Heine 95015045db implementation of environment variable passthrough
With this its possible to create custom environment variables within the kas
configuration file, that are passed through to the build environment:

    env:
      VARIABLE_NAME: "default variable value"

Those variables can be overwritten by variables of the environment kas is
started in:

    $ VARIABLE_NAME="overwritten variable value" kas shell ...

Those variables are also added to the 'BB_ENV_EXTRAWHITE' variable list to make
them available to bitbake.

This is useful for instance storing sensitive information, that should not be
part of the configuration files or bitbake recipes.

Signed-off-by: Claudius Heine <ch@denx.de>
2017-11-24 10:19:12 +01:00
docs implementation of environment variable passthrough 2017-11-24 10:19:12 +01:00
kas implementation of environment variable passthrough 2017-11-24 10:19:12 +01:00
scripts scripts: pep8 is renamed to pycodestyle 2017-11-08 09:46:00 +01:00
tests config: Added schema validation for configuration files 2017-10-13 14:11:10 +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 scripts: pep8 is renamed to pycodestyle 2017-11-08 09:46:00 +01:00
CHANGELOG.md Release 0.14.0 2017-11-02 16:02:33 +01:00
CONTRIBUTING.md Initial public release 2017-06-14 15:21:19 +02:00
docker-entrypoint docker: Avoid error messages on container restarts 2017-11-22 12:38:07 +01:00
Dockerfile Dockerfile: added less and vim 2017-08-01 09:35:17 +02:00
Dockerfile.isar docker: isar: configure sudo to keep proxy env variables 2017-11-02 16:16:34 +01: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 setup: added python 3.6 line 2017-11-10 09:21:42 +01: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.