Lines Matching +full:build +full:- +full:android
3 There are many ways to debug ANGLE using generic or platform-dependent tools. Here is a list of tips
23 `ldconfig -p | grep libGL`.
34 # edit samples/BUILD.gn and append "_static" to "angle_util", "libEGL", "libGLESv2"
35 ninja -C out/Debug
37 apitrace trace -o mytrace ./out/Debug/hello_triangle
43 Normally, ANGLE only logs errors and warnings (e.g. to Android logcat). General logging, or
54 If you want to enable `INFO`-level logs (and up) without incuring the log spam
60 ## Debug Angle on Android
62 Android is built as an Android APK, which makes it more difficult to debug an APK that is using ANG…
63 * You need to build ANGLE with debug symbols enabled. Assume your build variant is called Debug. Ma…
75 diff --git a/build/config/compiler/compiler.gni b/build/config/compiler/compiler.gni
77 --- a/build/config/compiler/compiler.gni
78 +++ b/build/config/compiler/compiler.gni
79 @@ -86,7 +86,8 @@ declare_args() {
83 - forbid_non_component_debug_builds = build_with_chromium
87 Build/install/enable ANGLE apk for your application following other instructions.
90 diff --git a/scripts/gdbclient.py b/scripts/gdbclient.py
92 --- a/scripts/gdbclient.py
94 @@ -395,6 +395,8 @@ def generate_setup_script(debugger_path, sysroot, linker_search_dir, binary_file
102 … the ANGLE source-file paths to what is visible to LLDB, which allows LLDB to show ANGLE's source …
103 …--shard-timeout 100000000` to disable the timeout so that the test won't get killed while you are …
105 ## Enabling Debug-Utils Markers
107 ANGLE can emit debug-utils markers for every GLES API command that are visible to both Android GPU
109 [enabling general logging](#enabling-general-logging) as well as setting the following additional
114 In addition, if the following GN arg is set, the API calls will output to Android's logcat:
120 ### Turning on Debug Markers on Android
122 On Android, debug markers are turned on and off with an Android debug property that is
135 variable (set in OS-specific manner):
145 tests with `--single-process-tests` argument.
147 ## Running ANGLE under GAPID on Android
150 command stream on Android. For it to work, ANGLE's libraries must have different names from the
158 …mium/src/+/main/third_party/angle/src/tests/test_utils/runner/android/java/src/com/android/angle/t…
159 based tests share the same activity name, `com.android.angle.test.AngleUnitTestActivity`.
161 When you build the test, a test launcher is generated, for example,
168 android.intent.action.MAIN:com.android.angle.test/com.android.angle.test.AngleUnitTestActivity
172 argument](https://developer.android.com/studio/command-line/adb.html#IntentSpec) for starting the
179 -e org.chromium.native_test.NativeTest.StdoutFile /sdcard/chromium_tests_root/out.txt -e org.chromi…
185 -e org.chromium.native_test.NativeTest.StdoutFile /sdcard/chromium_tests_root/out.txt --e org.chrom…
203 issue](https://github.com/baldurk/renderdoc/issues/1045#issuecomment-463999869). To capture Vulkan
204 traces, the workaround is to build RenderDoc without GL(ES) support.
210 $ sudo apt install libxcb-keysyms1-dev python3-dev qt5-qmake libqt5svg5-dev libqt5x11extras5-dev
213 $ cmake -DCMAKE_BUILD_TYPE=Release -Bbuild -H. -DENABLE_GLES=OFF -DENABLE_GL=OFF
216 $ QT_SELECT=5 make -j -C build
218 # Run RenderDoc from the build directory:
219 $ ./build/bin/qrenderdoc
230 if [ $# -lt 1 ]; then
237 if [ ! -d "$ver" ]; then
244 test -f "$ver"/x86_64/bin/vulkaninfo || exit 1
246 test -d "$ver"/x86_64/etc/explicit_layer.d || exit 1
248 test -d "$ver"/x86_64/lib || exit 1
256 echo sudo rm /usr/lib/x86_64-linux-gnu/libvulkan.so*
257 sudo rm /usr/lib/x86_64-linux-gnu/libvulkan.so*
258 echo sudo cp -P "$ver"/x86_64/lib/lib* /usr/lib/x86_64-linux-gnu/
259 sudo cp -P "$ver"/x86_64/lib/lib* /usr/lib/x86_64-linux-gnu/
264 ### Android subsection
267 If you are on Linux, make sure not to use the build done in the previous section. The GL renderer
272 # First delete the Cmake Cache in build/ directory
273 rm build/CMakeCache.txt
275 # Then build RenderDoc with cmake:
276 cmake -DCMAKE_BUILD_TYPE=Release -Bbuild -H.
277 QT_SELECT=5 make -j -C build
281 [Android Dependencies on Linux](https://github.com/baldurk/renderdoc/blob/v1.x/docs/CONTRIBUTING/De…
293 In the renderdoc directory, create Android builds of RenderDoc:
296 mkdir build-android-arm32
297 cd build-android-arm32/
298 cmake -DBUILD_ANDROID=On -DANDROID_ABI=armeabi-v7a ..
299 make -j
302 mkdir build-android-arm64
303 cd build-android-arm64/
304 cmake -DBUILD_ANDROID=On -DANDROID_ABI=arm64-v8a ..
305 make -j
310 …cumentation](https://github.com/baldurk/renderdoc/blob/v1.x/docs/CONTRIBUTING/Compiling.md#android)
313 When you run RenderDoc, choose the "Replay Context" from the bottom-left part of the UI (defaults to
323 Next, you need to install an ANGLE test APK. When you build the test, a test launcher is generated,
327 In RenderDoc, use `com.android.angle.test/com.android.angle.test.AngleUnitTestActivity` as the
331 -e org.chromium.native_test.NativeTest.StdoutFile /sdcard/chromium_tests_root/out.txt -e org.chromi…
335 dEQP on a non-default platform, the easiest way would be to modify `GetDefaultAPIName()` in
336 `src/tests/deqp_support/angle_deqp_gtest.cpp` (and avoid `--use-angle=X`).
342 use RenderDoc on Android. If you would like to build RenderDoc for Android on Windows yourself, you…
343 …umentation](https://github.com/baldurk/renderdoc/blob/v1.x/docs/CONTRIBUTING/Compiling.md#android).
344 We listed more detailed instructions below on how to set up the build on Windows.
346 ##### Install Android Dependencies
348 On windows, we need to install dependencies to build android, as described in
349 …entation](https://github.com/baldurk/renderdoc/blob/v1.x/docs/CONTRIBUTING/Dependencies.md#android)
350 1. Install [Android SDK](https://developer.android.com/about/versions/12/setup-sdk#install-sdk).
356 Value: path_to_sdk_directory (e.g. C:\Users\test\Appdata\Local\Android\Sdk)
357 2. Install [Android NDK](https://developer.android.com/studio/projects/install-ndk).
363 Value: path_to_ndk_directory (e.g. C:\Users\test\Appdata\Local\Android\Sdk\ndk\23.1.7779620)
373 5. Install [Android Debug Bridge](https://developer.android.com/studio/releases/platform-tools).
375 Append android_sdk_platform-tools_directory to the Path system variable.
377 e.g. C:\Users\Test\AppData\Local\Android\Sdk\platform-tools
380 ##### Install Build Tools
387 ##### Build RenderDoc Android APK on Windows
389 …using the Git Bash that comes with MinGW generator, you can run below commands to build Android APK
391 mkdir build-android-arm32
392 cd build-android-arm32/
393 cmake -DBUILD_ANDROID=On -DANDROID_ABI=armeabi-v7a -G "MinGW Makefiles" ..
394 make -j
397 mkdir build-android-arm64
398 cd build-android-arm64/
399 cmake -DBUILD_ANDROID=On -DANDROID_ABI=arm64-v8a -G "MinGW Makefiles" ..
400 make -j
406 …umentation](https://github.com/baldurk/renderdoc/blob/v1.x/docs/CONTRIBUTING/Compiling.md#android).
409 ##### Build Errors And Resolutions
429 Delete the CMakeCache file in build directories build-android-arm64/ or build-android-arm32/.
435 -Djava.ext.dirs is not supported.
445 1. Build arm32 and arm64 android packages. See [instructions](#build-renderdoc-android-apk-on-windo…
450 This step is required if you have installed / used RenderDoc on the same Android device before. Ren…
451 the renderdoccmd APK to the Android device if it finds the version of the existing APK on the devic…
459 3. Build renderdoc on windows desktop by clicking "build solution" in visual studio.
460 4. Launch renderdoc from visual studio, and push the android packages to android device by selectin…
463 ### Add SPIRV-to-GLSL Shader View Option
465 https://renderdoc.org/docs/window/settings_window.html#shader-processing-tools-config.
471 1. Get the SPIRV-Cross tool:
473 Clone the SPIRV-Cross git repo: https://github.com/KhronosGroup/SPIRV-Cross:
475 git clone https://github.com/KhronosGroup/SPIRV-Cross.git
477 Compile the SPIRV-Cross:
479 # inside SPIRV-Cross directory
482 2. Open Shader Viewer Settings window: RenderDoc -> Tools -> Settings, and select
487 |------------|-------------------------------------|
488 | Name | SPIRV-CROSS |
489 | Tool Type | SPIRV-Cross |
490 | Executable | <spirv-cross-repo-root>/spirv-cross |
505 2. Build ANGLE x64, Release.
512 `/opt/google/chrome-unstable`.
513 2. Build ANGLE for the running platform. `is_component_build = false` is suggested in the GN args.
515 4. Add ANGLE's build path to the `LD_LIBRARY_PATH` environment variable.
520 2. Build ANGLE for the running platform; GN args should contain `is_debug = false`.
527 - On Windows: `%LOCALAPPDATA%\Google\Chrome SxS\chrome.exe`
528 - On Linux: `/opt/google/chrome-unstable/google-chrome-unstable`
529 - On macOS: `./Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary`
531 With the following command-line options:
533 * `--use-cmd-decoder=passthrough --use-gl=angle` and one of
534 * `--use-angle=d3d9` (Direct3D 9 renderer, Windows only)
535 * `--use-angle=d3d11` (Direct3D 11 renderer, Windows only)
536 * `--use-angle=d3d11on12` (Direct3D 11on12 renderer, Windows only)
537 * `--use-angle=gl` (OpenGL renderer)
538 * `--use-angle=gles` (OpenGL ES renderer)
539 * `--use-angle=vulkan` (Vulkan renderer)
540 * `--use-angle=swiftshader` (SwiftShader renderer)
541 * `--use-angle=metal` (Metal renderer, macOS only)
545 * `--enable-logging`: To see logs
546 * `--disable-gpu-watchdog`: To disable Chromium's watchdog, killing the GPU process when slow (due
547 to a debug build for example)
548 * `--disable-gpu-sandbox`: To disable Chromium's sandboxing features, if it's getting in the way of
550 * `--disable-gpu-compositing`: To make sure only the WebGL test being debugged is run through ANGLE,