Skip to content

A
angle
Commit cffe90b4 by Ian Elliott Committed by Commit Bot
Options

Vulkan: Update documentation for enabling debug markers

After changes to the GN arg "angle_enable_trace" were done, other GN args are now needed. Bug: b/170249632 Change-Id: Ib5e703434cb580aa838ef8632b271f5f20554f42 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2684933Reviewed-by: 's avatarCody Northrop <cnorthrop@google.com> Reviewed-by: 's avatarTim Van Patten <timvp@google.com> Commit-Queue: Ian Elliott <ianelliott@google.com>
parent 7ec4d2d7
Showing with 6 additions and 2 deletions
doc/DebuggingTips.md
......@@ -41,10 +41,14 @@ qapitrace mytrace
## Enabling Debug Markers
ANGLE can emit debug-utils markers for every GLES API command that are visible to both Android
GPU Inspector (AGI) and RenderDoc. This support is compiled for debug builds or when the
following GN arg is set:
GPU Inspector (AGI) and RenderDoc. This support is compiled when the following GN args are set:
```
angle_enable_trace = true
angle_enable_annotator_run_time_checks = true
```
In addition, if the following GN arg is set, the API calls will output to Android's logcat:
```
angle_enable_trace_android_logcat = true
```
Once compiled, the markers need to be turned on.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment