cargo-binutils
cargo-binutils copied to clipboard
Cargo subcommands to invoke the LLVM tools shipped with the Rust toolchain
As per the https://docs.rust-embedded.org/embedonomicon/smallest-no-std.html, I execute the following. ```bash cargo nm -- target/thumbv7m-none-eabi/debug/deps/app-*.o | grep '[0-9]* [^N] ' /homeo/waleed/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/bin/llvm-nm: error: target/thumbv7m-none-eabi/debug/deps/app-2fb83299481625ce.o: No such file or directory ``` The binary is...
executed command: ``` cargo size --release --verbose -Z unstable-options ``` verbose output: ``` "/usr/local/rustup/toolchains/nightly-2022-06-15-x86_64-unknown-linux-gnu/bin/cargo" "build" "--release" "--message-format=json" error: the `--out-dir` flag is unstable, pass `-Z unstable-options` to enable it See...
expected: I only get `nm` output when redirecting/piping `cargo nm` standard output actual: `rustc`/`cargo` output is included as well: ``` ❯ cargo nm | head -11 Finished dev [unoptimized +...
This is personally motivated by the desire for easier interop with the `rustPlatform.buildRustPackage` nix tool which requires a `Cargo.lock` file to exist in the source git repository, however from memory...
It looks like rustc-cfg is unmaintained or at least dormant. There are no commits since October 2018, and it's dependence on failure (despite a PR to fix it) makes `cargo-audit`...
Seems to be caused by dependency chain "rustc-cfg 0.4.0" -> "failure 0.1.8" -> "backtrace 0.3.56" -> "object 0.23.0".
## Changes - Added more detail to error messages in `Tool::rust_exec`, Fixes: https://github.com/rust-embedded/cargo-binutils/issues/79 - Added target suggestion messages if no target was matched - Changed `cargo build` handling to collect...
Hi, on nightly with "-Zmultitarget" or in config.toml "multitarget=true" allows to define one or more "--target" parameters. Would be nice to have support for it here too. Best regards, TheAifam5