Differences
This shows you the differences between two versions of the page.
|
ep:labs:07:contents:tasks:ex3 [2025/05/04 16:55] radu.mantu |
ep:labs:07:contents:tasks:ex3 [2025/05/06 15:01] (current) radu.mantu |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| $ cmake --build profiler/build --config Release --parallel | $ cmake --build profiler/build --config Release --parallel | ||
| </code> | </code> | ||
| + | |||
| + | <note important> | ||
| + | If the compilation process takes up too much RAM, try to reduce the parallelization. | ||
| + | </note> | ||
| So far so good. Once we're done with the integration of the Client into our demo application, the Server will collect the trace data and process it for us. But first things first... | So far so good. Once we're done with the integration of the Client into our demo application, the Server will collect the trace data and process it for us. But first things first... | ||
| Line 28: | Line 32: | ||
| Recompile the project and make sure you don't have any errors. | Recompile the project and make sure you don't have any errors. | ||
| - | === [5p] Task C - Add trace marksers === | + | === [5p] Task C - Add trace markers === |
| Now that we have the **Tracy** client code compiled into our application, it's time to add some markers. Because we defined the **TRACY_ENABLE** macro at a global scale, the **FrameMark** macro has the following definition in ''Tracy.hpp'': | Now that we have the **Tracy** client code compiled into our application, it's time to add some markers. Because we defined the **TRACY_ENABLE** macro at a global scale, the **FrameMark** macro has the following definition in ''Tracy.hpp'': | ||
