sof/scripts
Janusz Jankowski 5dd9aaccb4 cmake: xtensa: use absolute paths for tools
CMake has convention of changing relative paths to absolute
for CMAKE_* variables. It does it automatically f.e. CMAKE_C_COMPILER.
However for our tools like objcopy we have to do it manually.
It also helps with integration of CMake in some IDEs.

Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-06-05 11:38:23 +02:00
..
cmake cmake: xtensa: use absolute paths for tools 2019-06-05 11:38:23 +02:00
docker_build license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
kconfig license: use spdx identifier in python files 2019-06-02 16:38:17 +01:00
README.docker scripts: remove all soft related stuff 2019-01-10 15:10:10 +00:00
build-tools.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
checkpatch.pl checkpatch: add spdx identifier 2019-06-02 16:38:17 +01:00
const_structs.checkpatch dai: supply caps and other info from within drivers 2019-05-03 03:14:43 -07:00
docker-qemu.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
docker-run.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
host-build-all.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
host-testbench.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
qemu-check.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
sof-post-commit-hook.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
sof-pre-commit-hook.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
sof-target-install.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00
sof_fw.kb ci: klocwork: add example config file to avoid FPs 2019-02-22 12:16:05 +01:00
spelling.txt sof: add git pre- and post-commit hooks 2018-01-23 21:08:05 +00:00
xtensa-build-all.sh license: use spdx identifier in shell scripts 2019-06-02 16:38:17 +01:00

README.docker

The docker container provided in docker_build sets up a build environment for
building Sound Open Firmware. A working docker installation is needed to run
the docker build container.

Note: In order to run docker as non sudo/root user please run.

sudo usermod -aG docker your-user-name

Then logout and login again.

Quick Start:

First, build the docker container. This step needs to be done initially and
when the toolchain or alsa dependencies are updated.

cd scripts/docker_build

./docker-build.sh

After the container is built, it can be used to run the scripts.

To build for baytrail:
./scripts/docker-run.sh ./scripts/xtensa-build-all.sh -l byt
or (may need password test0000 for rimage install)
./scripts/docker-run.sh ./scripts/xtensa-build-all.sh byt

To rebuild the topology and logger:
./scripts/docker-run.sh ./scripts/build-tools.sh

An incremental sof.git build:
./scripts/docker-run.sh make

Or enter a shell:
./scripts/docker-run.sh bash