A simple crate for passing spans generated by the tracing ecosystem to a C or C++ profiling system when Rust is integrated into an existing framework. To help with integration into other tools you can use the environment variable TRACING_FFI_RELATIVE_OUT_DIR to configure where the include file ends relative to the build output (OUT_DIR). For example, TRACING_FFI_RELATIVE_OUT_DIR = "../../../../../include" will normally lead to the files being generated in an include dir next to your Cargo.toml.

Example usage

#include <Profiling.h>
#include <tracing_ffi.h>
#include <myrustlib.h>

int main(int argc, const char* argv[]) {
    tracing_ffi_ReturnCode result = tracing_ffi_install_global_with_enable(
        profiling_begin_named_scope,
        profiling_end_named_scope,
        profiling_is_enabled,
    );

    if (result != tracing_ffi_ReturnCode_Success) {
        return (int)result;
    }

    myrustlib_execute(10, 20);

    profiling_write_file("profile.json");
}

You can of course also configure this from Rust code; and bypass the C-api. In that case, use subscriber::ExternFFISpanSubscriber directly, and install with your preferred tracing method.

Contribution

We welcome community contributions to this project.

Please read our Contributor Guide for more information on how to get started. Please also read our Contributor Terms before you make any contributions.

Any contribution intentionally submitted for inclusion in an Embark Studios project, shall comply with the Rust standard licensing model (MIT OR Apache 2.0) and therefore be dual licensed as described below, without any additional terms or conditions:

License

This contribution is dual licensed under EITHER OF

• Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

For clarity, "your" refers to Embark or any other licensee/user of the contribution.