Skip to content

Conversation

@cipharius
Copy link
Contributor

This provides a Tracy client integration which hooks into the existing arcan tracing facilities. Effectively that means the Tracy client specific code can be kept mainly confined in the arcan_trace.c, but with slightly more performance overhead compared to directly using Tracy API for marking execution zones.

As a side effect to this integration the CMake platform lists had to be refactored. During hybrid platform build phase, the C definitions got wiped, so platform specific build flags had to be seperated in order to keep global build flags intact.

This provides a Tracy client integration which hooks into the existing arcan tracing facilities.
Effectively that means the Tracy client specific code can be kept mainly confined in the arcan_trace.c, but with slightly more performance overhead compared to directly using Tracy API for marking execution zones.

As a side effect to this integration the CMake platform lists had to be refactored.
During hybrid platform build phase, the C definitions got wiped, so platform specific build flags had to be seperated in order to keep global build flags intact.
@letoram
Copy link
Owner

letoram commented May 15, 2023

LGMT, thanks.

@letoram letoram merged commit 7bf64a1 into letoram:master May 15, 2023
@cipharius cipharius deleted the feature/tracy-integration branch May 15, 2023 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants