mirror of
https://github.com/baldurk/renderdoc.git
synced 2026-05-05 09:30:44 +00:00
baldurk
c8a518f05c
* rdcstr no longer inherits from rdcarray, it implements all functionality itself. * There are now three representations: - Heap-allocated, same as how rdcarray behaves. - Local-allocated, for small strings we store them in a union array. - Compile-time literal, only created from user-defined literals. * The main observation is that a lot of RenderDoc's strings are compile-time literals either from struct names, member names, or stringified enum values. Storing these directly and allowing them to be moved and copied quickly saves on allocations and time. When the string is modified, it's copied to one of the other formats.
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.