Luca Barbato

Would be great to use always the pkg-config file so we'll avoid the problem of `- vs _`.

Static linking is often broken if you do not bring in the dependencies by some means, dynamic linking normally works since the dependencies are encoded in the dylib itself. pkg-config...

That use-case is unsupported because it is generally broken by design: either you have pkg-config telling you or you have to figure out by other means, such probing, the right...

Do not use `#include ` but `#include ""`

> > Do not use `#include ` but `#include ""` > > As mentioned above ([#217 (comment)](https://github.com/lu-zero/cargo-c/pull/217#discussion_r684646568)), I don't think this is the right thing to do (regardless whether it...

@gdesmott do you have any feedback/input about it?

cargo-c provides `-uninstalled.pc` files for that purpose, they have to be used explicitly as `--static` thought.

If you want to support uninstalled with shared library it requires to install the dylibs in a local path and patch the rpaths (in particular for macos)

It is the cleanest way that works for every platform, on macOS I'd have to invoke `install_name_tool` and patch up the binary to add the correct rpaths since there is...

I'll keep it open and try to document better how things should work.