Lines Matching refs:bindgen

14 - Build a C wrapper around the C++ code and use **[bindgen]** to translate that
23 covered.** You should use bindgen or cbindgen, or manually translated C
26 [bindgen]: https://github.com/rust-lang/rust-bindgen
35 implemented will cause a crash if you are lucky ([bindgen#388]) or more likely
36 silently emit an incompatible signature ([bindgen#380], [bindgen#607],
37 [bindgen#652], [bindgen#778], [bindgen#1194]) which will do arbitrary
40 [bindgen#388]: https://github.com/rust-lang/rust-bindgen/issues/388
41 [bindgen#380]: https://github.com/rust-lang/rust-bindgen/issues/380
42 [bindgen#607]: https://github.com/rust-lang/rust-bindgen/issues/607
43 [bindgen#652]: https://github.com/rust-lang/rust-bindgen/issues/652
44 [bindgen#778]: https://github.com/rust-lang/rust-bindgen/issues/778
45 [bindgen#1194]: https://github.com/rust-lang/rust-bindgen/issues/1194
47 Thus using bindgen correctly requires not just juggling all your pointers
51 returns std::unique\_ptr\<T\> through bindgen. Why? Because unique\_ptr, despite
53 containing a pointer ([bindgen#778]) and is not directly expressible in Rust.
73 When we make a binding for an idiomatic C++ API using bindgen, and we fall down
106 bindgen and cbindgen are built on top of `extern "C"`, it makes sense to think