267a53e78d
Bitbake provides a S3 fetcher (`lib/bb/fetch2/s3.py`), however the `AWS_CONFIG_FILE` and `AWS_SHARED_CREDENTIALS_FILE` variables are not transfered to the environment of the fetcher command (`aws` in this case) in the `runfetchcmd` function (`lib/bb/fetch2/__init__.py`). That means the location of these files need to be the default one, so copying it in KAS to the new HOME directory is necessary. This patch implements the copying of those files if the `AWS_CONFIG_FILE` and `AWS_SHARED_CREDENTIALS_FILE` are set. Per default there variables are not available in the bitbake environment. To have them available there a `env` entry in the kas configuration will be necessary. Signed-off-by: Claudius Heine <ch@denx.de> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
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.