Go to file
Abdur Rehman 5b85fba0df repos: use git diff-index to check if repo is dirty
is_dirty_cmd() uses `git diff --shortstat` to see if the repo can be
safely checked out. This only checks for the modified files and does
not take the cached(staged) files into account.

There can be cases where the cached changes could be overwritten by a
checkout. In this case, the git checkout command aborts with an error
message telling the user to commit or stash their changes.

Use `git diff-index HEAD --shortstat` to determine if there are any
changes in the tracked files, whether cached or not.

https://git-scm.com/docs/git-diff-index

Signed-off-by: Abdur Rehman <abdur_rehman@mentor.com>
2018-04-03 11:39:37 +02:00
docs implements patch support for repos 2018-03-09 09:59:07 +01:00
kas repos: use git diff-index to check if repo is dirty 2018-04-03 11:39:37 +02:00
scripts scripts: Remove the double Subject line from releases script 2018-03-07 09:22:27 +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.17.0 2018-02-08 15:49:56 +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: add iproute2 2018-01-29 10:07:24 +01:00
Dockerfile.isar docker: Add debootstrap to Isar image 2018-03-07 09:22:27 +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.