Question 1

How do I add Corrosion to my CMake project?

Accepted Answer

The easiest method is using CMake's FetchContent module, as demonstrated in the README: declare Corrosion with its Git repository and a version tag, make it available, and use corrosion_import_crate to import Rust targets from Cargo.toml.

Question 2

Can Corrosion handle Rust workspaces with multiple crates?

Accepted Answer

Yes, Corrosion can import targets from both package and workspace manifests in Cargo.toml, allowing it to manage multi-crate Rust projects seamlessly within CMake.

Question 3

Is Corrosion stable enough for production use?

Accepted Answer

Corrosion has active development and CI testing, but as a relatively young project, users should check the release notes for breaking changes and ensure compatibility with their CMake and Rust versions.

Question 4

Does Corrosion support dynamic libraries from Rust?

Accepted Answer

Yes, Corrosion can import dynamic libraries (shared libraries) from Rust crates, along with executables and static libraries, enabling flexible linking options in mixed-language builds.

Question 5

How do I cross-compile Rust code with Corrosion?

Accepted Answer

Corrosion integrates with CMake's toolchain files to simplify cross-compilation; set up your toolchain for the target platform, and Corrosion will handle the Rust-specific configurations automatically.

Question 6

Corrosion vs manual CMake scripts for Rust: which is better?

Accepted Answer

Corrosion automates boilerplate and ensures correct linking, reducing maintenance overhead and errors compared to manual scripts, especially for complex projects, but may add dependency management complexity.

corrosion

What is corrosion?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions