Re: [CMake] Debugging custom commands with VS project generator

> On 22 Jun 2017, at 11:52, David Cole wrote: > > When you convert that error code to hex, it's 0xc139, and if you > google that, you see it's an "entry point not found" error code. > > Is something in the custom command trying to load a DLL that doesn't > have the

Re: [CMake] Debugging custom commands with VS project generator

When you convert that error code to hex, it's 0xc139, and if you google that, you see it's an "entry point not found" error code. Is something in the custom command trying to load a DLL that doesn't have the expected export? Or perhaps trying to load a DLL of the wrong architecture? Or,

[CMake] Debugging custom commands with VS project generator

Hi, We’re trying to debug a failure of a custom build command, in a Cmake project using Visual Studio 2015. Unfortunately the command works on some Windows setups but not others - clearly there is something install-dependent going on. (It works on my local machine, but not on our Jenkins build