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
IDE name and version: CLion 2022.2.4 (CL-222.4345.21)
Operating system: Linux 6.0.7-arch1-1
Macro expansion: enabled
Problem description
The plugin is passing RUSTC_BOOTSTRAP=1 to build scripts sometimes (seems to only happen when you import a project without the target directory). This breaks build scripts that probe for nightly features, see #9235 for a similar bug.
Steps to reproduce
Create a project with a dependency that has a build script that probes for nightly features (e.g. thiserror)
Close Clion/Intellij
Delete the target directory of the project
Open the project in Clion/Intellij
Wait for background tasks to complete
Attempt to build/run the project
The project fails to build/run.
PR that might be related but I don't think(?) is relevant: #9637
The text was updated successfully, but these errors were encountered:
Since #9176 the plugin passes `RUSTC_BOOTSTRAP=1` environment variable to `cargo check` call to compiler and run as much as possible during build script evaluation phase (it's experimental feature of cargo that's why we need `RUSTC_BOOTSTRAP=1` here).
But this variable also is passed to `rustc` calls launched by cargo during compilation. And it may affect compilation. For example, compilation and evaluation of `thiserror` crate produce different results with different value of `RUSTC_BOOTSTRAP`.
Actually, we don't want to provide `RUSTC_BOOTSTRAP` to `rustc` invocations. So now the plugin stores original value of `RUSTC_BOOTSTRAP` in `INTELLIJ_ORIGINAL_RUSTC_BOOTSTRAP` (if it existed) environment variable and native helper passes it to `rustc`. It allows us to avoid some unexpected circumstances of `RUSTC_BOOTSTRAP=1`
Since intellij-rust#9176 the plugin passes `RUSTC_BOOTSTRAP=1` environment variable to `cargo check` call to compiler and run as much as possible during build script evaluation phase (it's experimental feature of cargo that's why we need `RUSTC_BOOTSTRAP=1` here).
But this variable also is passed to `rustc` calls launched by cargo during compilation. And it may affect compilation. For example, compilation and evaluation of `thiserror` crate produce different results with different value of `RUSTC_BOOTSTRAP`.
Actually, we don't want to provide `RUSTC_BOOTSTRAP` to `rustc` invocations. So now the plugin stores original value of `RUSTC_BOOTSTRAP` in `INTELLIJ_ORIGINAL_RUSTC_BOOTSTRAP` (if it existed) environment variable and native helper passes it to `rustc`. It allows us to avoid some unexpected circumstances of `RUSTC_BOOTSTRAP=1`
Environment
Problem description
The plugin is passing
RUSTC_BOOTSTRAP=1
to build scripts sometimes (seems to only happen when you import a project without thetarget
directory). This breaks build scripts that probe for nightly features, see #9235 for a similar bug.Steps to reproduce
thiserror
)target
directory of the projectPR that might be related but I don't think(?) is relevant: #9637
The text was updated successfully, but these errors were encountered: