I’ve got the latest version VS2017 and Physx 3.4, but I still get problems when I try to rebuild the libraries even after removing the error message. Many warning messages are reported which are now treated as errors. I got around this by changing the compile settings so the compiler ignores the warning and now all the solutions build and seem to run correctly. However this seems like a bad solution. Am I the only one seeing this behavior? If so there must be somrhign I am doing wrong. This is typical of the sort of error I see, this one when building SampleFramework-MT in release for x64:
C:\Program Files (x86)\Windows Kits\10\Include\10.0.16299.0\um\winbase.h(7356): error C2220: warning treated as error - no ‘object’ file generated (compiling source file …\src\SampleCommandLine.cpp)
C:\Program Files (x86)\Windows Kits\10\Include\10.0.16299.0\um\winbase.h(7356): warning C5039: ‘TpSetCallbackCleanupGroup’: pointer or reference to potentially throwing function passed to extern C function under -EHc. Undefined behavior may occur if this function throws an exception. (compiling source file …\src\SampleCommandLine.cpp)
As I say if I turn of the option for warnings to be treated as errors the project builds and seems to run but i get a variety of warnings in all of the projects and it worries me.