Luca Barbato

it is not something cargo-c controls but defers to cargo (the crate).

we look up what is in https://docs.rs/cargo/latest/cargo/util/config/struct.Config.html#method.load_global_rustc, I do not know how they are building cargo and how it is different from building the cargo crate as we build it.

it requires to know that you are in mingw64 reliably and I'm afraid it is not straightforward, but if you come up with a patch for it I'd be happy...

Do you have your code available so I can take a look?

It works as intended. cargo rejects setting features that aren't present in the manifest. I cannot work around this limitation without changing the cargo API.

there are two issues: - setting `cfg(cargo_c)` works but not for the tests because of how `cargo rustc` works, relaxing this constraint requires patching cargo. - adding on the fly...

It sounds a good idea indeed. :)

cbindgen let you blacklist types/functions/constants, so you can hide them from your .h and just add verbatim `#include` lines. I would spend energy in converting packages to use `system-deps` instead...

I'm thinking of making a new release of cargo-c this week, after we could see if we can make a proof-of-concept. I'll put down some [notes](https://hackmd.io/lrRugvY3S_y4OhYAoIogxA) on what we could...

Is this still a problem?