summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
author오형석/On-Device Lab(SR)/Staff Engineer/삼성전자 <hseok82.oh@samsung.com>2019-03-12 12:16:48 +0900
committerGitHub Enterprise <noreply-CODE@samsung.com>2019-03-12 12:16:48 +0900
commit9a34fc2693065fb68302d370ab3e1a945edb0b8b (patch)
tree9346a2be85cc5fe265a752372ede5d7689fa859c /docs
parent13234fc233a436d7dccd131d771e4690931d1616 (diff)
downloadnnfw-9a34fc2693065fb68302d370ab3e1a945edb0b8b.tar.gz
nnfw-9a34fc2693065fb68302d370ab3e1a945edb0b8b.tar.bz2
nnfw-9a34fc2693065fb68302d370ab3e1a945edb0b8b.zip
Update document to use docker image (#4677)
Update command usage and standalone scripts using docker image Signed-off-by: Hyeongseok Oh <hseok82.oh@samsung.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/howto/HowToUseDockerImage.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/howto/HowToUseDockerImage.md b/docs/howto/HowToUseDockerImage.md
index 978b9e8ed..890f9b96b 100644
--- a/docs/howto/HowToUseDockerImage.md
+++ b/docs/howto/HowToUseDockerImage.md
@@ -108,21 +108,21 @@ You can build docker image in your environment instead of pull docker image from
```
$ cd nnfw
-$ ./run build-docker
+$ ./nnfw build-docker
```
Default docker image name is `nnfw_docker`. If you want to change image name and/or tag, use `-t` or `--tag` option
```
$ cd nnfw
-$ ./run build-docker -t nnfw_docker_test
+$ ./nnfw build-docker -t nnfw_docker_test
```
You can use options supported by `docker build` command (ex. `--network` option)
```
$ cd nnfw
-$ ./run build-docker --network=host --no-cache
+$ ./nnfw build-docker --network=host --no-cache
```
If you want to build docker image for tizen build, use `--tizen` option
@@ -130,7 +130,7 @@ If you want to build docker image for tizen build, use `--tizen` option
```
```
$ cd nnfw
-$ ./run build-docker --tizen
+$ ./nnfw build-docker --tizen
```
```
@@ -143,10 +143,10 @@ Three different targets for `nnfw` can be built using docker image.
$ cd nnfw
$ docker run --rm -v $(pwd):/opt/nnfw -w /opt/nnfw nnfw_docker make install
```
-or use `docker_run_test.sh` for convenience as below.
+or use `docker_build_test_x64.sh` for convenience as below.
```
$ cd nnfw
-$ ./run docker_run_test.sh
+$ ./scripts/standalone/docker_build_test_x64.sh
```
You can find built artifacts at `nnfw/Product/x86_64-linux.debug`.
@@ -156,13 +156,13 @@ You should prepare RootFS, following [Cross Building for ARM](https://github.sec
```
$ cd nnfw
$ ROOTFS_DIR=$(pwd)/tools/cross/rootfs/arm \
-./run docker_build_cross_arm_ubuntu.sh
+./scripts/standalone/docker_build_cross_arm.sh
```
You can find built artifacts at `nnfw/Product/armv7l-linux.debug/`.
3. Build `nnfw` for Tizen ARM package on x86_64 host
```
$ cd nnfw
-$ ./run docker_gbs_build.sh
+$ ./scripts/standalone/docker_build_tizen_gbs.sh
```
You can find built artifacts at `Product/out/rpm`.