Daniel Pouzzner a3fb5029f8 clean up trailing whitespace and misplaced CRLFs, add missing final newlines, remove stray UTF8 nonprintables (BOMs) and ASCIIfy stray homoglyphs (spaces and apostrophes), guided by expanded coverage in wolfssl-multi-test check-source-text. | 3 months ago | |
---|---|---|
.. | ||
OpenWrt | 1 year ago | |
packaging | 1 year ago | |
wolfCLU | 3 months ago | |
yocto | 3 months ago | |
Dockerfile | 4 months ago | |
Dockerfile.cross-compiler | 8 months ago | |
README.md | 1 year ago | |
buildAndPush.sh | 3 months ago | |
include.am | 1 year ago | |
run.sh | 3 months ago |
This is a Docker environment for compiling, testing and running WolfSSL. Use run.sh
to build everything (Docker container, WolfSSL, etc.). This script takes in arguments that can be passed to ./configure
. For example: run.sh --enable-all
When the compilation and tests succeed, you will be dropped in to a shell environment within the container. This can be useful to build other things within the environment. Additional tests can be run as well as debugging of code.
These images are also uploaded to the wolfSSL's Docker Hub page. There is a convenience script here buildAndPush.sh
that will create the appropriate containers and push them to the repo.
You need to be added to the docker
group to run Docker containers. Run sudo usermod -aG docker $USER
. You may need to restart the Docker daemon.
The volume mounted in the Docker container needs to have all files that your compilation will need. To solve this, you have a couple options:
WOLFSSL_DIR
variable in the run.sh
to one higher up (by adding /..
to the path). Then update the docker build
to include the correct path to the Dockerfile and the docker run
argument to the working directory (-w
) to the WolfSSL source directoryexternal
folder which has your files. This route may have complications when stashing Git work.