Yes, memory manager is exposed to public. But the code that uses memory manager is entirely within DLL, including LibRaw class constructor and all methods.
The problem may occur only with link time code generation, but LibRaw.DLL do not use it.
Anyway, 4 different DLLs should solve the problem.
Yes, memory manager is exposed to public. But the code that uses memory manager is entirely within DLL, including LibRaw class constructor and all methods.
The problem may occur only with link time code generation, but LibRaw.DLL do not use it.
Anyway, 4 different DLLs should solve the problem.