renderdoc

mirror of https://github.com/baldurk/renderdoc.git synced 2026-05-18 07:51:14 +00:00

Files

T

baldurk 2484bc8bc7 Use UTF-8 everywhere possible and only use wchar_t where required.

* This means that all APIs pass byte string types. ALL strings everywhere
  in the entire codebase must be assumed to be and treated as UTF-8 content
  not ASCII.
* Gets rid of all the horrible %hs specifiers that caused warnings on
  linux! Hooray.
* We convert to wide strings, or use wide characters, only when necessary
  to use the Win32 API. Some windows specific code will stay in wide chars
  just for convenience.
* Files are already serialised as UTF-8 strings for linux/windows binary
  compatibility, so this change doesn't break backwards compatibility.

2014-11-23 14:45:16 +00:00

app

Use UTF-8 everywhere possible and only use wchar_t where required.

2014-11-23 14:45:16 +00:00

replay

Use UTF-8 everywhere possible and only use wchar_t where required.

2014-11-23 14:45:16 +00:00

README.md

Re-organise external-facing headers to be more easily used

2014-09-13 12:52:25 +01:00

README.md

This folder can be extracted out and placed into your source tree if you want to use RenderDoc.

If you want to access RenderDoc while it's injected into your program, the app/ folder is what you want. This also contains functions for injecting RenderDoc into existing or new processes.
If you want to write a program that utilises RenderDoc's replay and analysis capabilities (e.g. writing a new UI, or an auto-testing/offline analysis tool), the replay/ folder is what you want.

You will need both folders if you want to launch processes with RenderDoc injected.