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
The problem is that Intelij Rust invokes cargo with all-targets which doesn't work well for certain targets. Building the project manually with cargo build from the command line works just fine.
Compiling blinky v0.1.0 (D:\dev\projects\blinky)
error[E0463]: can't find crate for `test`
error: aborting due to previous error
For more information about this error, try `rustc --explain E0463`.
error: could not compile `blinky`.
To learn more, run the command again with --verbose.
Steps to reproduce
Have nightly-x86_64-pc-windows-gnu toolchain installed (ref rustc 1.44.0-nightly (6dee5f112 2020-04-06))
Install target thumbv7em-none-eabihf.
Create directory .cargo and config file in subdirectory.
The config file in this case specifies the target (see below):
The text was updated successfully, but these errors were encountered:
stianeklund
changed the title
error[E0463]: can't find crate for test
intellij-rust uses cargo --all-targets by default causing: error[E0463]: can't find crate for testApr 8, 2020
@mchernyavsky Thanks I tested this but it seems maybe that the build process hangs when I do this, however after updating to the latest nightly this issue no longer seems to be a problem.
Environment
Problem description
The problem is that
Intelij Rust
invokescargo
withall-targets
which doesn't work well for certain targets. Building the project manually withcargo build
from the command line works just fine.Somewhat related issues:
test
rust-lang/rls#1524Ref:
Steps to reproduce
nightly-x86_64-pc-windows-gnu
toolchain installed (refrustc 1.44.0-nightly (6dee5f112 2020-04-06
))thumbv7em-none-eabihf
..cargo
and config file in subdirectory.The config file in this case specifies the target (see below):
.cargo/config's contents:
Project was created from following steps at: https://github.com/stm32-rs/stm32f4xx-hal
The text was updated successfully, but these errors were encountered: