2020-11-13 01:23:57 +00:00
|
|
|
[package]
|
|
|
|
|
name = "bevy_log"
|
2021-04-06 18:48:48 +00:00
|
|
|
version = "0.5.0"
|
2020-11-13 01:23:57 +00:00
|
|
|
edition = "2018"
|
|
|
|
|
description = "Provides logging for Bevy Engine"
|
|
|
|
|
homepage = "https://bevyengine.org"
|
|
|
|
|
repository = "https://github.com/bevyengine/bevy"
|
2021-07-23 21:11:51 +00:00
|
|
|
license = "MIT OR Apache-2.0"
|
2020-11-13 01:23:57 +00:00
|
|
|
keywords = ["bevy"]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[dependencies]
|
2021-04-06 18:48:48 +00:00
|
|
|
bevy_app = { path = "../bevy_app", version = "0.5.0" }
|
|
|
|
|
bevy_utils = { path = "../bevy_utils", version = "0.5.0" }
|
2020-11-13 01:23:57 +00:00
|
|
|
|
Add trace_tracy feature for Tracy profiling (#2832)
# Objective
[Tracy](https://github.com/wolfpld/tracy) is:
> A real time, nanosecond resolution, remote telemetry, hybrid frame and sampling profiler for games and other applications.
With the `trace_tracy` feature enabled, you run your bevy app and either a headless server (`capture`) or a live, interactive profiler UI (`Tracy`), and connect that to your bevy application to then stream the metric data and events, and save it or inspect it live/offline.
Previously when I implemented the spans across systems and stages and I was trying out different profiling tools, Tracy was too unstable on macOS to use. But now, quite some months later, it is working stably with Tracy 0.7.8. You can see timelines, aggregate statistics of mean system/stage execution times, and much more. It's very useful!
## Solution
- Use the `tracing-tracy` crate which supports our tracing spans
- Expose via the non-default feature `trace_tracy` for consistency with other `trace*` features
2021-09-16 23:39:22 +00:00
|
|
|
tracing-subscriber = {version = "0.2.22", features = ["registry"]}
|
|
|
|
|
tracing-chrome = { version = "0.3.1", optional = true }
|
|
|
|
|
tracing-tracy = { version = "0.7.0", optional = true }
|
2020-11-13 01:23:57 +00:00
|
|
|
|
|
|
|
|
[target.'cfg(target_os = "android")'.dependencies]
|
|
|
|
|
android_log-sys = "0.2.0"
|
|
|
|
|
|
|
|
|
|
[target.'cfg(target_arch = "wasm32")'.dependencies]
|
|
|
|
|
console_error_panic_hook = "0.1.6"
|
2021-03-03 21:01:41 +00:00
|
|
|
tracing-wasm = "0.2"
|
2021-04-22 23:30:48 +00:00
|
|
|
|
|
|
|
|
[dev-dependencies]
|
|
|
|
|
bevy_internal = { path = "../bevy_internal", version = "0.5.0" }
|
