Bug description
Following #186, when a user traces a program with aligator with the profiling CMake option enabled, they obtain two different traces showing up in the tracy profiler. One will contain functions from libaligator and the other from libaligator_gar.
Expected behavior
One should only get a single trace.
Reproduction steps
Steps to reproduce the behavior:
- Compile aligator with the
ENABLE_TRACY_PROFILING flag
- Install the tracy profiler GUI
- Run
tracy-profiler
- Run for instance
TRACY_NO_EXIT=1 ./bin/aligator-example-clqr from the build directory
Additional context
The tracy manual's section 2.1.8 Setup for multi-DLL projects says that one should actually create a separate DLL/shared object which will contain the TracyClient symbols
Screenshots
System
- tracy 0.11.1
- aligator version: latest devel a30fc79
Bug description
Following #186, when a user traces a program with aligator with the profiling CMake option enabled, they obtain two different traces showing up in the tracy profiler. One will contain functions from
libaligatorand the other fromlibaligator_gar.Expected behavior
One should only get a single trace.
Reproduction steps
Steps to reproduce the behavior:
ENABLE_TRACY_PROFILINGflagtracy-profilerTRACY_NO_EXIT=1 ./bin/aligator-example-clqrfrom the build directoryAdditional context
The tracy manual's section 2.1.8 Setup for multi-DLL projects says that one should actually create a separate DLL/shared object which will contain the TracyClient symbols
Screenshots
System