It looks like I do indeed combine the /clr and /EHa switch for the CLR and /EHs is indeed not compatible with /clr
So /clr and /EHa are correct, I suspect adding the C++/CLR support to visual studio helped it.
I will add a switch to the Pulse superbuild to turn off the CLR build if you don’t want to mess with managed code in MSVC, The PulseCLR project will not be created so I will leave it enabled by default, so the project will be created. I will also add notes to the readme explaining this.
Concerning the last two error screen shots. They seem to be two different errors related to two seperate compilers.
1.) For some reason, ninja in msvc is not processing a post build command properly. I have not hooked up ninja in my visual studio environment, so I will need to do this and see what exactly is it complaining about and why. I pulled Pulse into a directory with a space in the path, as well as created a build directory with a space in the path and had no issue building, so I am suspecting ninja is not liking something somewhere… I will see if I can get ninja up and running on my windows system and see what the bad $-escape error is… I do use some specific MSVC macros when building through MSVC, so I suspect niinja does not know what to do with those macros…
2.) For the Qt error, are you building Debug? It seems as if the libprotobufd.lib was not built for some reason, or is not in the expected location… I can try and see what that error is as well.
There are lots of ways to compile a program and I have not tried these combinations… Only vanilla MSVC on windows