Allow use of `cargo-xbuild` and tooling
See original GitHub issueEnvironment
- IntelliJ Rust plugin version: 0.2.105.2133-192
- Rust toolchain version: nightly-2019-09-05-x86_64-unknown-linux-gnu
- IDE name and version: Clion 2019.2.1
- Operating system: Arch-Linux 5.2.13-arch1-1-ARCH
Problem description
The plugin does not really allow to use xcheck
and xclippy
which are provided by the https://github.com/rust-osdev/cargo-xbuild crate, which is a simplified version of xargo
. The plugin should allow to select xcheck
and xclippy
as the linter because the check
and clippy
tasks don’t work when using xbuild
.
A cool extra idea which came to my mind was to also allow debugging with xrun
if set up manually. For example, I’m launching via qemu which allows debugging, but somehow attaching doesn’t seem to correctly load the symbols. I however know that it is possible to use Clion to debug native code in qemu because I once did it with C++ and it worked perfectly. Maybe this can be somehow reflected by this plugin (of course I know this with qemu is a very specific case, however since this is gcc one might be able to generalize it).
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:6 (1 by maintainers)
Being able to just switch compiler/command with xbuild/xcheck/xclippy would already be pretty good
Do you still need support for
cargo-xbuild
? It’s possible to build stdlib modules via cargo now. https://github.com/rust-osdev/cargo-xbuild#alternative-the-build-std-feature-of-cargo. Looks like it makesxbuild
tool quite redundant