Executing application fails with code 0xc0000135 during build

[pasbi]

I have a rather complicated build setup:
First, a command line executable (ommpfritt-cli) is built, then it is executed in order to generate some icons, which are then bundled into the actual application (ommpfritt).

The problem is, that on windows, execution of ommpfritt-cli fails with code 0xc0000135 (apparently a DLL is missing).
I have the same setup on my local windows (MinGW) machine (same packages installed, same dlls in the build directory), and it works.
It also works on travis with ubuntu.

I don’t know how to debug this, please advice!

Travis CI - Test and Deploy Your Code with Confidence

[native-api]

See diagnosis steps in this post:

Failing to run compiled Python extension

Bottom line: change compiler flags to link to libgcc and libstdc++ statically. Or place them (with any transitive MinGW-specific dependencies) alongside the .pyd and distribute with your module. I’ve diagnosed the problem with Process Monitor using the following code. This is the most reliable way because you get to see what the system is actually searching for, and where, rather than look at metadata and make assumptions. Since Windows’ DLL search process is compilcated and very settings-de…