Jonathan Schwender

> I suspect however that the original idea of using this property was to respect's CMake's choice of linker (via CMAKE__LINKER_PREFERENCE), which is something that goes away with this workaround...

> I was trying to figure out how corrosion's LINKER_LANGUAGE works and found that the value is always empty. I can confirm that. If `tgt` is a rust crate (so...

@ogoffart Since we have released version `0.1`, I would go ahead and merge this and the other open PR if that is okay with you.

I had another look at this, and openend issue #133 for a more general discussion of what we should do.

Closing, since #208 deprecated corrosion_set_linker_language.

Hi, sorry for the late reply. I personally don't use macOS, so the most I can offer is to review a PR implementing such a feature.

This should be possible via `cargo vendor`. The required configuration should be written to a [`.cargo/config.toml`](https://doc.rust-lang.org/cargo/reference/config.html). The `.cargo/config.toml` must be located in a parent of the CMake *build* directory to...

Have you considered using "sccache" to cache your compilation results?

Instead of adding the dummy `example` library, you should also be able to to use [add_dependencies](https://cmake.org/cmake/help/latest/command/add_dependencies.html): `add_dependencies(your_android_target rust_target)`. I think this is basically just a side effect of corrosion exposing...

If you are not doing anything else with the rust library, it would probably be easier to just add `cargo build ` as a custom command to CMake and copy...