c1e5c4f379
pycodestyle v2.4.0 checks for W606 (async deprecated), but we can't disable it on source code level with '# noqa'. Let's disable the check globaly. We will still catch it with pylint. By disabling the W606 we need also to list the W503 which was previously active. While at it fix following things: ./docs/conf.py:252:6: E121 continuation line under-indented for hanging indent ./docs/conf.py:257:6: E126 continuation line over-indented for hanging indent ./kas/build.py:123:17: W504 line break after binary operator ./kas/configschema.py:48:25: E123 closing bracket does not match indentation of opening bracket's line ./kas/configschema.py:49:21: E123 closing bracket does not match indentation of opening bracket's line ./tests/test_includehandler.py:82:13: E123 closing bracket does not match indentation of opening bracket's line ./tests/test_includehandler.py:121:13: E123 closing bracket does not match indentation of opening bracket's line Signed-off-by: Daniel Wagner <daniel.wagner@siemens.com> |
||
|---|---|---|
| docs | ||
| kas | ||
| scripts | ||
| tests | ||
| .dockerignore | ||
| .gitignore | ||
| .pylintrc | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| docker-entrypoint | ||
| Dockerfile | ||
| Dockerfile.isar | ||
| LICENSE | ||
| README.rst | ||
| requirements_rtd.txt | ||
| run-kas | ||
| setup.py | ||
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.