ID:132416
 
I seem to have hit across an issue with my DLL String Utilities library, where something between BYOND and my DLL do not match up. BYOND (I assume) is compiled in Visual C++, where-as my library is compiled in MinGW.

Locally my DLL works fine, but other people's systems it does not, producing a "not found" error for my DLL, and no output even if they compile it for themselves from source with Visual C++.

I suppose there is a good chance this isn't a runtime linkage issue. but I'd like to rule it out. My test harness for C++ links this fine and it executes fine.

My library is linked with the following options:
-Wl,--enable-auto-import

This enables automatic import of libstdc++, as MinGW hides the import lib away somewhere. I currently do not, (but have the option to) compile with -mthreads, which as I understand is similar to Visual C++'s /MT option. The threading model of my DLL is Win32.

I'm happy to provide further information, discover what it's linking against etc.
I will take to installing Visual Studio and giving it a whirl in there. For reference, I am on Windows XP x64, and most testers thus far have been on Windows 7 x64.