我可以通过猜测我试图从 c 绑定到 rust 的库是“命名空间”来解决这个问题,在 C 语言中实际上没有命名空间,但是编写开源代码的人倾向于在他们的代码前面加上“some_prefix *” . 因此,如果我要绑定的 h 文件如下所示:
mylib.h:
include <hello.h>;
include <bye.h>;
include <hola.h>;
...
mylib_add_value(...);
mylib_remove_value(...);
mylib_display_value(...);
...
而且我不希望生成 hola.h,我可以使用 bingden 的允许和阻止功能过滤输出,例如:
构建.rs:
fn main() {
// Tell cargo to tell rustc to link the system nvpair of zfs
// shared library.
println!("cargo:rustc-link-lib=mylib");
// The bindgen::Builder is the main entry point
// to bindgen, and lets you build up options for
// the resulting bindings.
let bindings = bindgen::Builder::default()
// The input header we would like to generate
// bindings for.
.header("wrapper.h")
.allowlist_var(r#"(\w*mylib\w*)"#)
.allowlist_type(r#"(\w*mylib\w*)"#)
.allowlist_function(r#"(\w*mylib\w*)"#)
.blocklist_item(r#"(\w*hola\w*)"#)
.blocklist_type(r#"(\w*hola\w*)"#)
.blocklist_function(r#"(\w*hola\w*)"#)
.clang_args(vec!["-I/usr/include/mylib"])
.default_enum_style(bindgen::EnumVariation::Rust {
non_exhaustive: (true),
})
// Finish the builder and generate the bindings.
.generate()
// Unwrap the Result and panic on failure.
.expect("Unable to generate bindings");
// Write the bindings to the $OUT_DIR/bindings.rs file.
let out_path = PathBuf::from(env::var("OUT_DIR").unwrap());
bindings
//.write_to_file(out_path)
.write_to_file(out_path.join("bindings.rs"))
.expect("Couldn't write bindings!");
}
Bindgen 会先把所有的白名单的依赖都带进来,如果有的依赖包含进来*hola*
就不会生成。