Lines Matching +full:vulkan +full:- +full:tools
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`.
35 ninja -C out/Debug
37 apitrace trace -o mytrace ./out/Debug/hello_triangle
54 If you want to enable `INFO`-level logs (and up) without incuring the log spam
75 diff --git a/build/config/compiler/compiler.gni b/build/config/compiler/compiler.gni
77 --- a/build/config/compiler/compiler.gni
79 @@ -86,7 +86,8 @@ declare_args() {
83 - forbid_non_component_debug_builds = build_with_chromium
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 …om `/your_path_to_chromium_src/out/Debug` folder. This adds the ANGLE source-file paths to what is…
103 …--shard-timeout 100000000` to disable the timeout so that the test won't get killed while you are …
122 ## Enabling Debug-Utils Markers
124 ANGLE can emit debug-utils markers for every GLES API command that are visible to both Android GPU
126 [enabling general logging](#enabling-general-logging) as well as setting the following additional
152 variable (set in OS-specific manner):
157 ## Enable Vulkan Call Logging
159 ANGLE can output Vulkan API call information including detailed parameter info and state. Vulkan
166 By default Vulkan call logging goes to stdout, or logcat on Android. Vulkan call logging can be
167 …ace event and debug marker output as shown in [enabling general logging](#enabling-general-logging)
168 and [enabling Debug-Utils markers](#enabling-debug-utils-markers)
170 ### Vulkan Call Logging on Desktop
172 To log Vulkan calls on desktop set the environment variable `ANGLE_ENABLE_VULKAN_API_DUMP_LAYER` to…
174 For Vulkan call logging output to a file, set
177 To show only Vulkan api calls without verbose parameter details set the environment variable
180 ### Vulkan Call Logging on Android
182 Activate Vulkan call logging on Android by setting this Android debug property that is
188 For Vulkan call logging to a file on Android, specify the filename with an Android debug property t…
201 [GAPID](https://github.com/google/gapid) can be used to capture trace of Vulkan commands on Linux.
203 tests with `--single-process-tests` argument.
207 [GAPID](https://github.com/google/gapid) can be used to capture a trace of the Vulkan or OpenGL ES
230 argument](https://developer.android.com/studio/command-line/adb.html#IntentSpec) for starting the
237 -e org.chromium.native_test.NativeTest.StdoutFile /sdcard/chromium_tests_root/out.txt -e org.chromi…
243 -e org.chromium.native_test.NativeTest.StdoutFile /sdcard/chromium_tests_root/out.txt --e org.chrom…
261 issue](https://github.com/baldurk/renderdoc/issues/1045#issuecomment-463999869). To capture Vulkan
268 $ sudo apt install libxcb-keysyms1-dev python3-dev qt5-qmake libqt5svg5-dev libqt5x11extras5-dev
271 $ cmake -DCMAKE_BUILD_TYPE=Release -Bbuild -H. -DENABLE_GLES=OFF -DENABLE_GL=OFF
274 $ QT_SELECT=5 make -j -C build
280 If your distribution does not provide a recent Vulkan SDK package, you would need to manually
288 if [ $# -lt 1 ]; then
295 if [ ! -d "$ver" ]; then
302 test -f "$ver"/x86_64/bin/vulkaninfo || exit 1
304 test -d "$ver"/x86_64/etc/explicit_layer.d || exit 1
306 test -d "$ver"/x86_64/lib || exit 1
314 echo sudo rm /usr/lib/x86_64-linux-gnu/libvulkan.so*
315 sudo rm /usr/lib/x86_64-linux-gnu/libvulkan.so*
316 echo sudo cp -P "$ver"/x86_64/lib/lib* /usr/lib/x86_64-linux-gnu/
317 sudo cp -P "$ver"/x86_64/lib/lib* /usr/lib/x86_64-linux-gnu/
334 cmake -DCMAKE_BUILD_TYPE=Release -Bbuild -H.
335 QT_SELECT=5 make -j -C build
339 …ub.com/baldurk/renderdoc/blob/v1.x/docs/CONTRIBUTING/Dependencies.md#android-dependencies-on-linux)
354 mkdir build-android-arm32
355 cd build-android-arm32/
356 cmake -DBUILD_ANDROID=On -DANDROID_ABI=armeabi-v7a ..
357 make -j
360 mkdir build-android-arm64
361 cd build-android-arm64/
362 cmake -DBUILD_ANDROID=On -DANDROID_ABI=arm64-v8a ..
363 make -j
371 When you run RenderDoc, choose the "Replay Context" from the bottom-left part of the UI (defaults to
389 -e org.chromium.native_test.NativeTest.StdoutFile /sdcard/chromium_tests_root/out.txt -e org.chromi…
393 dEQP on a non-default platform, the easiest way would be to modify `GetDefaultAPIName()` in
394 `src/tests/deqp_support/angle_deqp_gtest.cpp` (and avoid `--use-angle=X`).
408 1. Install [Android SDK](https://developer.android.com/about/versions/12/setup-sdk#install-sdk).
415 2. Install [Android NDK](https://developer.android.com/studio/projects/install-ndk).
431 5. Install [Android Debug Bridge](https://developer.android.com/studio/releases/platform-tools).
433 Append android_sdk_platform-tools_directory to the Path system variable.
435 e.g. C:\Users\Test\AppData\Local\Android\Sdk\platform-tools
438 ##### Install Build Tools
449 mkdir build-android-arm32
450 cd build-android-arm32/
451 cmake -DBUILD_ANDROID=On -DANDROID_ABI=armeabi-v7a -G "MinGW Makefiles" ..
452 make -j
455 mkdir build-android-arm64
456 cd build-android-arm64/
457 cmake -DBUILD_ANDROID=On -DANDROID_ABI=arm64-v8a -G "MinGW Makefiles" ..
458 make -j
487 Delete the CMakeCache file in build directories build-android-arm64/ or build-android-arm32/.
493 -Djava.ext.dirs is not supported.
503 1. Build arm32 and arm64 android packages. See [instructions](#build-renderdoc-android-apk-on-windo…
521 ### Add SPIRV-to-GLSL Shader View Option
522 RenderDoc allows us to add and configure customized shader processing tools:
523 https://renderdoc.org/docs/window/settings_window.html#shader-processing-tools-config.
529 1. Get the SPIRV-Cross tool:
531 Clone the SPIRV-Cross git repo: https://github.com/KhronosGroup/SPIRV-Cross:
533 git clone https://github.com/KhronosGroup/SPIRV-Cross.git
535 Compile the SPIRV-Cross:
537 # inside SPIRV-Cross directory
540 2. Open Shader Viewer Settings window: RenderDoc -> Tools -> Settings, and select
545 |------------|-------------------------------------|
546 | Name | SPIRV-CROSS |
547 | Tool Type | SPIRV-Cross |
548 | Executable | <spirv-cross-repo-root>/spirv-cross |
570 `/opt/google/chrome-unstable`.
585 - On Windows: `%LOCALAPPDATA%\Google\Chrome SxS\chrome.exe`
586 - On Linux: `/opt/google/chrome-unstable/google-chrome-unstable`
587 - On macOS: `./Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary`
589 With the following command-line options:
591 * `--use-cmd-decoder=passthrough --use-gl=angle` and one of
592 * `--use-angle=d3d9` (Direct3D 9 renderer, Windows only)
593 * `--use-angle=d3d11` (Direct3D 11 renderer, Windows only)
594 * `--use-angle=d3d11on12` (Direct3D 11on12 renderer, Windows only)
595 * `--use-angle=gl` (OpenGL renderer)
596 * `--use-angle=gles` (OpenGL ES renderer)
597 * `--use-angle=vulkan` (Vulkan renderer)
598 * `--use-angle=swiftshader` (SwiftShader renderer)
599 * `--use-angle=metal` (Metal renderer, macOS only)
603 * `--enable-logging`: To see logs
604 * `--disable-gpu-watchdog`: To disable Chromium's watchdog, killing the GPU process when slow (due
606 * `--disable-gpu-sandbox`: To disable Chromium's sandboxing features, if it's getting in the way of
608 * `--disable-gpu-compositing`: To make sure only the WebGL test being debugged is run through ANGLE,