Mateusz Mikuła

I haven't seen issue like that but there were many other reports, maybe are you using software which injects dlls to running processes? You might want to check https://cygwin.com/faq/faq.html#faq.using.bloda

To be honest number of false positives from MSE/Windows 10 Defender is overwhelming. Both of them would randomly detect threat when updating MSYS2 and virustotal just proves it was false...

@niklasholm you can exclude MSYS2 directory in your AV.

I'm not using Avast but usually there are 2 separate exclude directories, one for the scanner and one for the real-time protection.

> Remove the separate crates for gnullvm targets (https://github.com/microsoft/windows-rs/pull/1961) Yeah, that will work as long as nothing CRT specific lands in import libs. > Further down the road, I'm planning...

If somebody can confirm there are no CRT specific differences (in other words: they do **not** pull other import libraries from SDK/mingw-w64 during creation) between import libraries of these two...

Almost any crate could be cross compiled to windows-gnu from Linux host. Building the std is also simple since MinGW can be installed from the repo. I'll do the investigation...

Okay so without modifying try builds there are 2 possibilities that will work with `no_std` rlib crates like `winapi-rs`: - `cargo xbuild --target x86_64-pc-windows-{gnu,msvc}` - first run will build required...

With https://github.com/rust-lang/rust/pull/51241/ available since two releases (or three releases in few days) this should be considered again. If machine running the benchmarks has fairly recent glibc (at least 2.26) this...

FYI there is PR to RA which seems to add similar functionality: https://github.com/rust-lang/rust-analyzer/pull/13490. It also resulted in creating PR for Rust to expose this functionality: https://github.com/rust-lang/rust/pull/103693