just a follow up:

Out of curiosity, I tried to compile some old DKit plugins I wrote 15 years ago in Visual Studio 2012 on windows 7. Other than some warnings about deprecated standard C library functions, they compile successfully. However, I ran into a few link errors I could not figure out how to resolve:

1>dkit.lib(tinyFcurve.obj) : error LNK2001: unresolved external symbol __adj_fdivr_m64 1>dkit.lib(tinyFcurve.obj) : error LNK2001: unresolved external symbol __adjust_fdiv 1>dkit.lib(tinyFcurve.obj) : error LNK2001: unresolved external symbol __adj_fdiv_r 1>dkit.lib(tinyFcurve.obj) : error LNK2001: unresolved external symbol __adj_fdiv_m32 1>E:\dev\projects\si3d\Release\checker.exe : fatal error LNK1120: 4 unresolved externals


Online I found an old microsoft KB article which describes the problem as one specific to visual studio 2.0/2.1:

   http://support.microsoft.com/kb/128895

Unfortunately, the suggested workaround of using the "/QIfdiv-" compiler option is no longer recognized by today's visual studio. Unless I can find the modern day equivalent, I'll need to use Visual C++ v6.0. :-(


Matt

Reply via email to