From cea0a5977a23a15d2c180c171df0b51bf678645c Mon Sep 17 00:00:00 2001 From: Darren Rush Date: Wed, 21 Nov 2018 17:59:56 -0800 Subject: [PATCH] docs: enable tinygo/docker to resolve go dependencies Example for mapping the GOPATH into the tinygo docker image so that go dependencies installed on the host can be found by the image. --- docs/docker.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/docker.rst b/docs/docker.rst index 5cdeb23f..94ff8e3d 100644 --- a/docs/docker.rst +++ b/docs/docker.rst @@ -19,7 +19,14 @@ To compile ``blinky1.hex`` targeting an AVR microcontroller such as the Arduino: docker run --rm -v $(pwd):/src tinygo/tinygo build -o /src/blinky1.hex -size=short -target=arduino examples/blinky1 -Note that for microcontroller development you must flash your hardware devices +For projects that have remote dependencies outside of the standard library and go code within your own project, you will need to map your entire GOPATH into the docker image in order for those dependencies to be found:: + + docker run -v $(PWD):/mysrc -v $GOPATH:/gohost -e "GOPATH=$GOPATH:/gohost" tinygo/tinygo build -o /mysrc/wasmout.wasm -target wasm /mysrc/wasm-main.go + +.. note:: + At this time, tinygo does not resolve dependencies from the /vendor/ folder within your project. + +For microcontroller development you must flash your hardware devices from your host environment, since you cannot run ``tinygo flash`` from inside the docker container.