Closed Brett208 closed 4 years ago
Thank you for looking into this.
Can you push the changes to a branch? It looks like there is some mixing of debug and release builds. The two are likely binary incompatible, so if you force linking of the wrong one, bad things can happen. It's unclear to me if this is a static library or DLL build of Google Test.
Added PR #248 as requested.
There doesn't appear to be a static build of Google Test available for install via vcpkg (I'm new to vcpkg so may have missed it).
See the appveyor build for details. It passed with release and failed for debug, so I guess that rules out my local machine being the problem.
-Brett
We need to find a gtest dependency that allows us to use gmock on MSVC builds and set MSVC compilations as C++17 compliant. C++17 compliance is required for nesting namespace declarations.
I have continued working with vcpkg. I have OP2Utility compiling locally with the following settings:
I'm not really sure how to (Press Retry to debug the application).
Any help on this would be appreciated. I feel close to getting vcpkg's gtest install to work, but I'm stuck and doubt that I will make much more progress on my own.
-Brett