Jonathan Schwender

If that doesn't work out, feel free to have a look at removing the `.cargo/config` and passing the rustflags directly. We do already support setting rustflags (see `corrosion_add_target_rustflags`), you would...

> I'm working on a [code generator](https://github.com/KDAB/cxx-qt) that generates C++ headers which need to be available in a predictable location for target_include_directories. You could also generate files to some location...

> The C++ dependency is absent when invoking cargo on the command line directly and is introduced by corrosion when it sets the CORROSION_LINKER_PREFERENCE variable cmake/Corrosion.cmake which is eventually passed...

As for testing: > Would this be a new directory under test/? Yes > Should I create different tests to with and without the native tools or is this somehow...

https://github.com/corrosion-rs/corrosion/pull/208 added an option to explicitly set the linker for a target, which should also fit your usecase.

I guess it does make the documentation more complex, but fundamentally you can compile the generator on a different machine and ship it together with the corrosion cmake files to...

Looking at this, it seems we could add a small abstraction for this to corrosion rather easily, since the configuration seems to be done in the `cbindgen.toml` file. We could...

Do you need any new features (i.e. something that is not supported yet by corrosion), or would it be acceptable for you to stay on a v0.2 branch and just...

Thanks for the report. I guess we will have to add a special case for the "dev" profile, since unfortunately the output directory name is not the same as the...

This issue is pretty old already, but I thought I'd leave some comments here anyway: > I'm using corrosion_import_crate(MANIFEST_PATH Cargo.toml) and it's not clear which target name I need to...