8b91666943
We just need to lift the dist for that target to xenial - but not to bionic because 3.4 is then no longer supported. In xenial, mercurial is part of travis image. Additionally installing it is not needed and actually breaks things. But things are more complicated because hg is under /usr/local/bin, and kas used a built-in PATH for tools that does not include this. At this chance, remove "sudo: required" - no longer needed. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> |
||
---|---|---|
docs | ||
kas | ||
scripts | ||
tests | ||
.dockerignore | ||
.gitignore | ||
.travis.yml | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
docker-entrypoint | ||
Dockerfile | ||
Dockerfile.isar | ||
kas-docker | ||
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.