Luca Barbato
Luca Barbato
cargo-c uses cargo's settings, so if you set the linker it would pick it. What does FreeBSD do for the normal cargo packages?
`CARGO_TARGET__LINKER=the-compiler-you-want` should take care of it.
You may set a `config.toml` https://doc.rust-lang.org/cargo/reference/config.html?highlight=linker#configuration-format that is potentially even nicer given how many settings you want to pass. But this is not related to cargo-c itself so probably it...
You actually always "cross compile" when using clang or rustc. And it gets even more important since cargo has a partial understanding on which flags go with the host build...
You always have a triple. I would suggest you to ask on the cargo zulip and solve it also for the rest of the rust packages.
You possibly are trying to copy files in a location you cannot access with your current user, try to ``` cargo cinstall --destdir /tmp/staging sudo cp -a /tmp/staging/* / ```
It would be needed to support overlays properly, but even in that case it would be an incremental improvement over the core feature itself. Maybe could be spun away so...
rustfmt seems unhappy and the CI seems to fail to build speexdsp
`git2` is a dependency coming from https://crates.io/crates/built, if you open a pr to forward the feature selection and I'd land it immediately.
How does it break?