diff options
| author | Sean Harmer <sean.harmer@kdab.com> | 2014-10-25 14:34:16 +0100 |
|---|---|---|
| committer | Sean Harmer <sean.harmer@kdab.com> | 2014-10-26 10:17:22 +0100 |
| commit | 0e7ac3d230879986d9353c13eed4b45038f3eee4 (patch) | |
| tree | 15a7a72a747485dd78c83dbb23765eb4383b3cec /examples/gltf/main.cpp | |
| parent | a4e2aaca2faf6d65999ff1153631dbc253d1a1df (diff) | |
Disable debug output by default for Qt3D
It is possible to override this, e.g. if you need more debug logging,
by specifying a categorised logging file by means of the QT_LOGGING_CONF
environment variable. For example to enable debug logging on a bunch
of categories create a text file containing the following:
[Rules]
Qt3D.Core.Nodes.debug=true
Qt3D.Core.Aspects.debug=true
Qt3D.Core.Resources.debug=true
Qt3D.Core.ChangeArbiter.debug=true
Qt3D.Render.Backend.debug=true
Qt3D.Render.Frontend=.debug=true
Qt3D.Render.IO.debug=true
Qt3D.Render.Jobs.debug=true
Qt3D.Render.Framegraph.debug=true
Qt3D.Render.RenderNodes.debug=true
Qt3D.Render.Rendering.debug=true
Qt3D.Render.Memory.debug=true
And then set this as the active rules by pointing QT_LOGGING_CONF at
the file. You can verify where the logging rules are coming from by
defining the QT_LOGGING_DEBUG environment variable.
Change-Id: Iad3824c6db0b7f22c417b06734204c666a2ee8dd
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
Diffstat (limited to 'examples/gltf/main.cpp')
0 files changed, 0 insertions, 0 deletions