Generating bindings to C library

[remote hill]

what happens if you run cargo doc --no-deps --open? Does it show any members in the crate?

K, then you should have everything set up right

You don't see any output because it's only temporary

The temp file is somewhere in the targets/ folder probably

If you use the items as shown in the docs above, or from another package you should be able to access them. You can try it out by making some examples in examples/

You can see how to make examples for libraries at http://xion.io/post/code/rust-examples.html (the https is broken for some reason)

For tests https://doc.rust-lang.org/rust-by-example/testing/unit_testing.html should help

It will keep using that one until something changes to the header file

Awesome, ask if you have any other issues

[remote hill]

This should have been setup in the build script link search path

You can use https://github.com/rust-lang/libc for libc types and functions. Including them in your library is dependant on situation

Oh, you can't put a relative path: it needs to be absolute thirdparty\\opengr2\\libopengrn\\

Recommend to use something like

let manifest_dir = var("CARGO_MANIFEST_DIR").unwrap();

println!("cargo:rustc-link-search={}/libraries/lib/arm-linux-gnueabihf", manifest_dir);