-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specifying the manifest path ignores .cargo/config.toml #10302
Labels
C-bug
Category: bug
Comments
@ehuss thanks for the quick response! I would add though that I tried adding the |
It should, unless something else is overriding it. Can you show a complete example? For example:
|
uncomfyhalomacro
added a commit
to openSUSE-Rust/obs-service-cargo
that referenced
this issue
Nov 17, 2024
…directory when invoking commands This is to address this weird issue in rust-lang/cargo#10302. Related issues about `cargo` improvements are tracked here in rust-lang/cargo#12738. Currently, to do this manually, it must be set to the parent path of Cargo.toml. Signed-off-by: Soc Virnyl Estela <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: