You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying --manifest-path=dir/Cargo.toml the .cargo/config.toml files appear to be ignored. It doesn't seem to matter whether .cargo/config.toml is (e.g., in my crates, workspace, or the directory from which I am running Cargo). It is always ignored.
Steps
Place some configuration in a .cargo/config.toml file. For example, I have:
[build]
target = "wasm32-unknown-unknown"
So that Cargo compiles to WebAssembly by default.
2. Run cargo build --manifest-path=path/to/Cargo.toml
3. Observe that instead of WebAssembly, Cargo is producing shared libraries (i.e., .so on Linux)
@ehuss thanks for the quick response! I would add though that I tried adding the .cargo directory with the config.toml inside it to the working directory to no avail.
Problem
When specifying
--manifest-path=dir/Cargo.toml
the.cargo/config.toml
files appear to be ignored. It doesn't seem to matter whether.cargo/config.toml
is (e.g., in my crates, workspace, or the directory from which I am running Cargo). It is always ignored.Steps
.cargo/config.toml
file. For example, I have:So that Cargo compiles to WebAssembly by default.
2. Run
cargo build --manifest-path=path/to/Cargo.toml
3. Observe that instead of WebAssembly, Cargo is producing shared libraries (i.e.,
.so
on Linux)Possible Solution(s)
No response
Notes
No response
Version
The text was updated successfully, but these errors were encountered: