Known issuesΒΆ

  • Statically linking multiple Kanzi Rust libraries in a single application is not supported.

    Workaround: Link your Rust modules in a single crate and register metadata of your Rust plugins there, without registering the plugins themselves:

use kanzi::IPlugin;

MyPlugin1::default().register_metadata_override(&domain)?;
MyPlugin2::default().register_metadata_override(&domain)?;

  • Kanzi Rust API leaks ThreadObject instances stored in non-Kanzi thread when they outlive the Kanzi thread.

    Workaround: Drop ThreadObject instances before the Kanzi thread exits.

  • When building Kanzi Rust API code from Visual Studio, the builder can fail with the FTK1011 error. This happens because the internal MSBuild file tracker does not support paths that exceed MAX_PATH.

    Workaround: Update your build environment and set the TrackFileAccess environment variable to false. Keep in mind that this change causes incremental builds to stop working. You can set the environment variable in .cargo/config.toml:

    [env]
TrackFileAccess = "false"