Luca Barbato

> I am setting the linker, from that very variable: https://github.com/BtbN/FFmpeg-Builds/blob/master/scripts.d/50-rav1e.sh#L45 Or is there some other undocumented way to set the linker? It is documented you can set it via...

It is a fix, you have to set the correct environment variables :) https://docs.rs/system-deps/latest/system_deps/#overriding-build-flags

let me open https://github.com/gdesmott/system-deps/issues/62 and see if we can fix it better.

We can move the discussion on the system-deps issue and probably we can try to improve the situation at cargo level (or in `cargo-c` since I guess you'll get through...

Having that part clarified and/or possibly replaced with something less unexpected would be a boon indeed (the patch referred and the follow up is still pending since it had deemed...

While oxidizing speexdsp I stumbled upon this problem + the more generic one of having to produce 1 library and many headers. Could be possible to add a way to...

If you want a reduced testcase I tripped in the same problem with: ``` type Complex = num_complex::Complex; pub const CONST: i32 = 42; ```

If you want to produce a C-API library from your crate you might prefer to use [cargo-c](https://github.com/lu-zero/cargo-c) instead of using cbindgen from build.rs on a crate you would also publish...

@pkgw please use `cargo-c`, this kind of custom solution is a nightmare for distributions.

I assumed you wanted to have the actual library installed on the system, sorry for the noise.