/MT flag uses static C runtime libraries. Microsoft says using /MT flag is not recommended if you pass STL objects across dll interfcae (and it causes various heap corruption errors). You can search in MSDN for more details. Brook+ runtime has a different dll for CAL backend and brook.dll and brook_cal.dll contain STL objects in their exported interfaces.
You can build source with Release_CRTDLL configuration and it should work fine.
Originally posted by: gaurav.garg
/MT flag uses static C runtime libraries. Microsoft says using /MT flag is not recommended if you pass STL objects across dll interfcae (and it causes various heap corruption errors). You can search in MSDN for more details. Brook+ runtime has a different dll for CAL backend and brook.dll and brook_cal.dll contain STL objects in their exported interfaces.
You can build source with Release_CRTDLL configuration and it should work fine.
Yes, it should be possible. But, then you have to change brook_cal.dll also to static library. Also, Brook+ runtime loads this dll at runtime, you need to change that code.