Marcus Lindblom wrote:
Check that you're linking with the same runtime libs as the OpenSG-dlls you're using. (check this by searching for msvcrt71.dll or msvcrt71D.dll in your file and in OpenSG's libraries).

(There ought to be some way of checking this, either during build or during runtime. I can't think of one at the moment though.)
(Just had an idea about this).

Actually, one could make a mechanism for this. Since the VC compiler defines _DEBUG, _DLL and _MT depending on which runtime-libs you compile against, it would be quite easy to write something in the header file (say osgInit.h) that pass this information (i.e. the client application's settings) to the compiled dll's in OpenSG, which can then issue a warning.

I'll see if I can cook something up that solves this.

/Marcus


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to