a84b64761c
Optionally extract build artifacts from an archive file instead of
building them. This completes the separation between building the tests
and running them. To use this, do something like:
go run test-compile.go
Arrange to have the mcuboot dir and the test-images.zip on the test
target, and then run:
go run run-tests.go -prebuilt test-images.zip
Signed-off-by: David Brown <david.brown@linaro.org>
|
||
|---|---|---|
| .. | ||
| bad-keys | ||
| hello-world | ||
| mcutests | ||
| .gitignore | ||
| Makefile | ||
| README.md | ||
| build-boot.sh | ||
| build-hello.sh | ||
| overlay-ecdsa-p256.conf | ||
| overlay-rsa.conf | ||
| overlay-skip-primary-slot-validate.conf | ||
| overlay-upgrade-only.conf | ||
| run-tests.go | ||
| run-tests.sh | ||
| test-compile.go | ||
README.md
Zephyr sample application.
In order to successfully deploy an application using mcuboot, it is necessary to build at least one other binary: the application itself. It is beyond the scope of this documentation to describe what an application is able to do, however a working example is certainly useful.
Please see the comments in the Makefile in this directory for more details on how to build and test this application.
Note that this sample uses the "ninja" build tool, which can be installed on most systems using the system package manager, e.g., for a Debian-based distro:
$ sudo apt-get install ninja
or in Fedora:
$ sudo dnf install ninja