On 23/09/2014 at 03:25, xxxxxxxx wrote:
Cinema 4D Version: R16
Platform: Windows ;
Language(s) : C++ ;
we are currently updating our plugin to the R16 SDK from R15 (R15 builds work fine).
We have updated the R16 SDK/framework to use VS2013 and the v120 toolset. The SDK/framework builds are also fine. We are using the Debug target and the 64bit version.
If we build our plugin (we have updated all includes etc.) we are experiencing a linker error during linking of the "cinema.framework_Debug_64bit.lib" with our plugin.
error LNK2038: mismatch detected for '_MSC_VER': value '1700' doesn't match value '1800' in PluginName.obj
It's strange because we are using the v120 Toolset in all of the involved projects. Intellisense is also telling us the _MSC_VER is 1800 in both, c4d sdk/framework and our plugin (although we don't trust it that much, but a debug build with printing the compiler version is also correct.)
- Do you guys use precompiled headers with an older compiler version (even the flag for not using them is set)?
- You have stated, the SDK is very well compatible with VS2012 and newer in the documentation, is this also the case with updated VS2013 from VS2012 projects?
- Are you setting the _MSC_VER during the compilation of the framework manually? (we could not find anything like that either in the sdk src)
- Is your Intelcompiler using a different vc++ compiler version? Sadly we have no access to the compiler you used and we believe that's not really a problem but anyway.
Did i miss anything? Every tip is very well appreciated.
We really want to use VS2013. So downgrading for 2012 is not really an option for us right now.
- What is the meaning of the LibDebug, LibRelease and LibIntel targets? Is this something special to consider? (We tried using both libraries, LibDebug and Debug. No effect.)
Thanks for your time in advance and have a nice day!
I just quickly portet it (the plugin) back to VS Express 2012. Works fine. So it's a compiler problem?