Closed Latias94 closed 1 year ago
I'll publish a bump to 0.14.1 soon, probably within the next day. (staging the change here.. https://github.com/aclysma/profiling/tree/candidate-1.0.7)
I published 1.0.7 which uses newer tracy bindings.
I noticed in one of my projects when enabling tracy, I needed to change this:
#[cfg(feature = "profile-with-tracy")]
profiling::tracy_client::set_thread_name("Main Thread");
to
#[cfg(feature = "profile-with-tracy")]
profiling::tracy_client::Client::start();
#[cfg(feature = "profile-with-tracy")]
profiling::tracy_client::set_thread_name!("Main Thread");
(add call to Client::start() and make set_thread_name() a macro.)
FYI this is a breaking change if tracy profiling is enabled. Semver for this crate is only promised when all features are off. (profiling is only meant to be enabled locally, so published crates should never have enabled profiling features.) Bumping crate versions would result in fragmentation, somewhat self-defeating for the intent of this crate to let users instrumented-profile all the things.
I think this breaking change is introduced from profiling = "=1.0.6"
, see https://github.com/aclysma/profiling/pull/36.
Update the
tracy-client
dependency since https://github.com/nagisa/rust_tracy_client/issues/51 has been resolved.Test success with
profiling = { git = "https://github.com/Latias94/profiling", branch = "tracy-0.14.1" }