Discussion
https://doc.rust-lang.org/cargo/reference/config.html#config-relative-paths
Note: To maintain consistency with existing
.cargo/config.tomlprobing behavior, it is by design that a path in a config file passed via--config <path>is also relative to two levels up from the config file itself.
It Is By Design
https://doc.rust-lang.org/cargo/reference/config.html#executable-paths-with-arguments
If the path to the executable contains a space, the list form must be used.
Cargo Parses
If the specified program does not have path separators, Cargo will search
PATHfor its executable.
Cargo Will Search
Support for the
.tomlextension was added in version 1.39. In version 1.68, Cargo writes to the file with the extension by default. However, for backward compatibility reason, when both files exist, Cargo will read and write the file without the extension.
For Backward Compatibility Reason
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#paths-overrides
Sometimes you’re only temporarily working on a crate and you don’t want to have to modify
Cargo.tomllike with the[patch]section above. For this use case Cargo offers a much more limited version of overrides called path overrides.
Cargo Offers
Path overrides are specified through
.cargo/config.tomlinstead ofCargo.toml. Inside of.cargo/config.tomlyou’ll specify a key calledpaths:paths = ["/path/to/uuid"]This array should be filled with directories that contain a
Cargo.toml.
You'll Specify A Key
As a result, usage of a path override is typically isolated to quick bug fixes rather than larger changes.
As A Result
this is fucking absurd https://doc.rust-lang.org/cargo/reference/config.html#buildrustc
build.rustcType: string (program path)
Default:"rustc"
Environment:CARGO_BUILD_RUSTCorRUSTCSets the executable to use for rustc.
so "Type: string (program path)" is it a string or a program path? does it get split by space? does it get looked up by PATH? oh my god fuck--
build.rustc-wrapperType: string (program path)
Default: none
Environment:CARGO_BUILD_RUSTC_WRAPPERorRUSTC_WRAPPERSets a wrapper to execute instead of
rustc. The first argument passed to the wrapper is the path to the actual executable to use (i.e.,build.rustc, if that is set, or"rustc"otherwise).
a wrapper that introspects the rustc. very cool, very normal, very UX. but there's even MORE UX
build.rustc-workspace-wrapperType: string (program path)
Default: none
Environment:CARGO_BUILD_RUSTC_WORKSPACE_WRAPPERorRUSTC_WORKSPACE_WRAPPERSets a wrapper to execute instead of
rustc, for workspace members only. When building a single-package project without workspaces, that package is considered to be the workspace. The first argument passed to the wrapper is the path to the actual executable to use (i.e.,build.rustc, if that is set, or"rustc"otherwise). It affects the filename hash so that artifacts produced by the wrapper are cached separately.If both
rustc-wrapperandrustc-workspace-wrapperare set, then they will be nested: the final invocation is$RUSTC_WRAPPER $RUSTC_WORKSPACE_WRAPPER $RUSTC.
The Final Invocation
You need to log in to see that page.
Install bonfire.cafe
Get the full app experience
