New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use devenv.com instead of devenv.exe #28
Conversation
Hm, seems like the failure is legit although unrelated to this particular PR. While setting up sanitizers (for #26) it complains about
|
Looks like it's always reproduced now on CI. Unfortunately I don't have much time to look into it, help appreciated! (I've sent you an invitation to collaborate on this project.) |
We could disable that test for now to unblock this PR. |
Thanks for the invite <3 Think I'll try fixing that bug first. If I shouldn't be able to do that then we can disable the test. |
Note: CI in master currently fails due to a just released new version of bitflags which causes breakage: bitflags/bitflags#251 |
bitflags 1.3.0 was yanked. Just need a rebase to get this PR ready to merge. |
For some reason on some Visual Studio installs devenv.exe just returns immediately with an error code and runs the build in the background. It also doesn't emit any output via stdout/stderr. According to [1] devenv.com is the executable to use for build output via stdout/stderr and it doesn't misbehave so switch to that. [1]: https://docs.microsoft.com/en-us/visualstudio/ide/reference/devenv-command-line-switches?view=vs-2019
For some reason on some Visual Studio installs* devenv.exe just returns
immediately with an error code and runs the build in the background. It
also doesn't emit any output via stdout/stderr. According to 1
devenv.com is the executable to use for build output via stdout/stderr
and it doesn't misbehave so switch to that.
*In my case it fails with Visual Studio 2022 Preview but works on another (virtual) machine with Visual Studio 2019. But if I install deinstall 2019 and install 2022 in that VM then it also works so I honestly have no idea why the behavior differs. But since it's documented that devenv.com is for stdout/stderr usage I think it makes sense to switch regardless.