Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 GN | 1 GN |
| 2 ===== | 2 ===== |
| 3 | 3 |
| 4 [GN](https://chromium.googlesource.com/chromium/src/tools/gn/) | 4 [GN](https://chromium.googlesource.com/chromium/src/tools/gn/) |
| 5 is a new meta-build system originally designed to replace GYP in Chromium. | 5 is a new meta-build system originally designed to replace GYP in Chromium. |
| 6 | 6 |
| 7 You can build Skia using GN in a limited number of configurations. We expect | 7 You can build Skia using GN in a limited number of configurations. We expect |
| 8 that as that limited number rises, GN will become the preferred, and then only, | 8 that as that limited number rises, GN will become the preferred, and then only, |
| 9 way to build Skia. | 9 way to build Skia. |
| 10 | 10 |
| (...skipping 63 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 74 gn gen out/arm --args='ndk="/tmp/ndk" target_cpu="arm"' | 74 gn gen out/arm --args='ndk="/tmp/ndk" target_cpu="arm"' |
| 75 gn gen out/arm64 --args='ndk="/tmp/ndk" target_cpu="arm64"' | 75 gn gen out/arm64 --args='ndk="/tmp/ndk" target_cpu="arm64"' |
| 76 gn gen out/mips64el --args='ndk="/tmp/ndk" target_cpu="mips64el"' | 76 gn gen out/mips64el --args='ndk="/tmp/ndk" target_cpu="mips64el"' |
| 77 gn gen out/mipsel --args='ndk="/tmp/ndk" target_cpu="mipsel"' | 77 gn gen out/mipsel --args='ndk="/tmp/ndk" target_cpu="mipsel"' |
| 78 gn gen out/x64 --args='ndk="/tmp/ndk" target_cpu="x64"' | 78 gn gen out/x64 --args='ndk="/tmp/ndk" target_cpu="x64"' |
| 79 gn gen out/x86 --args='ndk="/tmp/ndk" target_cpu="x86"' | 79 gn gen out/x86 --args='ndk="/tmp/ndk" target_cpu="x86"' |
| 80 | 80 |
| 81 Other arguments like `is_debug` and `is_component_build` continue to work. | 81 Other arguments like `is_debug` and `is_component_build` continue to work. |
| 82 Tweaking `ndk_api` gives you access to newer Android features like Vulkan. | 82 Tweaking `ndk_api` gives you access to newer Android features like Vulkan. |
| 83 | 83 |
| 84 To test on a locally connected Android device, you can use our `droid` convenien ce script: | 84 To test on an Android device, push the binary and `resources` over, |
| 85 and run it as normal. You may find `bin/droid` convenient. | |
| 85 | 86 |
| 86 <!--?prettify lang=sh?--> | 87 <!--?prettify lang=sh?--> |
| 87 | 88 |
| 88 ninja -C out/arm64 | 89 ninja -C out/arm64 |
| 89 bin/droid out/arm64/dm --src gm --config gpu | 90 adb push out/arm64/dm /data/local/tmp |
| 91 adb push resources /data/local/tmp | |
|
csmartdalton
2016/09/16 19:25:09
Resources are specific to the dm binary itself as
mtklein_C
2016/09/16 19:30:56
I see your point but every app we have to use as a
| |
| 92 adb shell "cd /data/local/tmp; ./dm --src gm --config gpu" | |
| OLD | NEW |