[]
= "tracers-dyn-stap"
= "0.1.0"
= ["Adam Nelson <anelson@127.io>"]
= "2018"
= "MIT OR Apache-2.0"
= """
Implements the dynamic probing API using `libstapsdt`, which in turn uses Linux SystemTap underneath.
Do not use this crate directly. Always use the `tracers` crate and let it auto-detect which implementation
to use.
"""
= "https://github.com/anelson/tracers"
# This is a hack. Or maybe a workaround for a bug.
#
# It seems that Cargo does not pass variables to dependent crates using the DEP_(PKGNAME)_(VARNAME)
# env vars unless it thinks the crate is wrapping a native library. This package is definitely not
# doing that, but setting this in the manifest ensures that the downstream dependency `tracers` build.rs
# can query the variables produced by this `build.rs` to detect if stap is available for us or not
#
# This will be unnecessary once https://github.com/rust-lang/cargo/issues/3544 is implemented
= "tracers-dyn-stap"
[]
# by default, building the stap provider is disabled. It must be explicitly enabled
= []
# if this feature is enabled, then the build.rs will try to build the stap provider's
# dependencies, libstapstd-sys (and, transitively, libelf-sys).
# if the build fails, this crate's build will still succeed, but the stap provider's code
# will not be included in the resulting crate.
#
# The success or failure of the build will be communicated via a variable in cargo,
# which dependent crates can resolve with DEP_TRACERS_STAP_SUCCEEDED
= ["tracers-libstapsdt-sys/enabled"]
# If this feature is enabled, it implies `enabled`, and also will cause the build to fail if
# the stap provider cannot be built
= ["tracers-libstapsdt-sys/required"]
[]
= { = "../tracers-libstapsdt-sys", = "0.1.0", = true }
= "0.1.6"
= "1.2.0"
[]
= "../tracers-core"
= "0.1.0"
= ["dynamic"]
[]
= "0.1.6"
[]
= "0.9.0"
= "0.8.0"
= "0.2.65"