Nicolas Abram

@jrmuizel Were you able to figure out why you were missing the directory in your installation? I wonder if there is some optional component in the VS installer for the...

Ohh, I understand now. So you had multiple SDKs and you wanted the skip the one without the include files. That explains why you didn't get linker errors, since that...

Would the correct place to do this be around here? https://github.com/alexcrichton/cc-rs/blob/388bf178f6c857bb07bcc333ceb31032fbee686c/src/lib.rs#L2901-L2908 Just test for *.bat or *.cmd and if so change the command to cmd and prepend the "/c "{command}"...

Weird, I just ran a build of the cc-test test crate in this repo with `AR=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\lib.exe` and it worked Could you check again, against the master...

I was looking for the same thing. Maybe it could be a separate derive like AddRef to avoid bloating current users of derive_more with additional code they don't need

Would it make sense for this crate to support named pipes on windows?

I'm also running into this. I tried adding the verbose flag but it change nothing.

I'm getting this same issue when using quicksilver, not sure which dependency is causing it.

I think the panic happens on this line https://github.com/koute/cargo-web/blob/4dce4505fcaba3e816bb00126dc2e8a1ddea14e7/src/cargo_shim/mod.rs#L415 Could we add to the panic messsage the dependency name?

The rust issue was closed/resolved: The rust issue was closed: https://github.com/rust-lang/rust/issues/48792#issuecomment-538651489