suricata/rust/ffi/Cargo.toml.in

[package]
name = "suricata-ffi"
version.workspace = true
edition.workspace = true
rust-version.workspace = true
license.workspace = true
description = "Nice wrappers around Suricata C interface"

[dependencies]
suricata-sys = { path = "../sys", version = "@PACKAGE_VERSION@" }

[features]
debug = []
debug-validate = []
testing = []
rust/ffi: stub out a rust ffi crate This crate is for Rust wrappers around the -sys crate which includes only raw bindings. This is the place to add nice wrappers around those bindings, however it should remain clear of dependencies on the main Suricata core crates. Ticket: #7666 9 months ago			`[package]`
			`name = "suricata-ffi"`
rust: inherit common package metadata from workspace 2 weeks ago			`version.workspace = true`
			`edition.workspace = true`
			`rust-version.workspace = true`
			`license.workspace = true`
rust/ffi: stub out a rust ffi crate This crate is for Rust wrappers around the -sys crate which includes only raw bindings. This is the place to add nice wrappers around those bindings, however it should remain clear of dependencies on the main Suricata core crates. Ticket: #7666 9 months ago			`description = "Nice wrappers around Suricata C interface"`
rust/ffi: add logging (debug) wrappers Mostly a copy of Suricata core's logging wrappers into the ffi crate. These are not yet used by Suricata-core as they do require the Suricata library to be available, which is not the case with tests. And the `cfg(test)` parameter is not passed through to sub-crates. However, this does allow a plugin (or library) to call the logging macros without depending on the "suricata" crate. Ticket: #7666 9 months ago
			`[dependencies]`
rust/ffi: specify sys crate dependency version This is required for crates.io publishing, and we also use this for other internal crate dependencies, for example suricata depending on derive, etc. 4 months ago			`suricata-sys = { path = "../sys", version = "@PACKAGE_VERSION@" }`
rust/ffi: add logging (debug) wrappers Mostly a copy of Suricata core's logging wrappers into the ffi crate. These are not yet used by Suricata-core as they do require the Suricata library to be available, which is not the case with tests. And the `cfg(test)` parameter is not passed through to sub-crates. However, this does allow a plugin (or library) to call the logging macros without depending on the "suricata" crate. Ticket: #7666 9 months ago
			`[features]`
			`debug = []`
rust/ffi: move debug validations macros to ffi Ticket: 7666 6 months ago			`debug-validate = []`
rust/ffi: move AppLayerTxData to ffi Ticket: 7666 6 months ago			`testing = []`