From 4beff4e9d4f449e30591951488bd3335a2acf2a1 Mon Sep 17 00:00:00 2001 From: chrysn Date: Wed, 21 Aug 2024 21:53:10 +0200 Subject: [PATCH] makefiles: Align cargo-info output with what happens in the build system This simplifies the explanation of what might need adjustments depending on which cargo command is invoked. --- makefiles/info.inc.mk | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/makefiles/info.inc.mk b/makefiles/info.inc.mk index 271a428313..9c9f683d01 100644 --- a/makefiles/info.inc.mk +++ b/makefiles/info.inc.mk @@ -250,9 +250,10 @@ info-rust: cargo version c2rust --version @echo "To use this setup of Rust in an IDE, add these command line arguments to the \`cargo check\` or \`rust-analyzer\`:" - @echo " --target $(RUST_TARGET) --profile $(CARGO_PROFILE) $(CARGO_OPTIONS)" + @echo " --profile $(CARGO_PROFILE) $(CARGO_OPTIONS)" @echo "and export these environment variables:" + @echo " CARGO_BUILD_TARGET=\"$(RUST_TARGET)\"" @echo " RIOT_COMPILE_COMMANDS_JSON=\"$(CARGO_COMPILE_COMMANDS)\"" @echo " RIOTBUILD_CONFIG_HEADER_C=\"$(RIOTBUILD_CONFIG_HEADER_C)\"" @echo "You can also call cargo related commands with \`make cargo-command CARGO_COMMAND=\"cargo check\"\`." - @echo "Beware that the way the profile and other flags are passed in is not consistent across cargo commands, so adding \`--profile $(CARGO_PROFILE)\` or other flags from above as part of CARGO_COMMAND may be necessary." + @echo "Beware that the way command line arguments are passed in is not consistent across cargo commands, so adding \`--profile $(CARGO_PROFILE)\` or other flags from above as part of CARGO_COMMAND may be necessary."