Thanks heaps! yfede, I moved to MSVC 2015 in the meantime as someone figured out how to build dlls xp-compatible if required. This is described in another thread:
Yes this does help! Using visual studio 2015 update 2, the 140_xp toolset and the /Zc:threadSafeInit- I was able to build a plugin that loads on Windows XP. So finally I can erase VS2013. The explanation (by Microsoft) on the thread you linked is rather interesting, so I’ll copy it here as well:
Windows Server 2003 and Windows XP have problems with dynamically loading a DLL (via LoadLibrary) that uses thread-local storage, which is what thread-safe statics use internally to provide efficient e…
