VS 2013 - a word of caution

On 08/12/2013 at 04:13, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   Any 
Platform:   Windows  ;   
Language(s) :     C++  ;

---------
If you plan to use VS 2013 please have a look into this blog entry:

http://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/

Microsoft created a potential incompatibility in the class layout of 64 bit compiles of the new compiler - this can create trouble and hard to spot bugs when working with software that was compiled with ANY prior VS edition.

You can try applying the workaround mentioned in that blog (although that can get pretty ugly) or refrain from using VS 2013...

Best regards,

Wilfried

On 08/12/2013 at 05:52, xxxxxxxx wrote:

Hi Wilfried,
thanks for this! Yes, I plan to use VS 2013 eventually. But for the C4D plugins I write, this will probably not have any influence at all? I compile for 32 and 64 bit.

On 08/12/2013 at 08:42, xxxxxxxx wrote:

Oh wonderful.
Thanks Microsoft. You're the gift that just keeps on giving.  :angry:
Does this mean that Maxon is going to be sticking with VS2012 then?

I tried compiling the R15 demo with VS2013. But I couldn't, because it required the vs110 toolset that comes with VS2012.
I was going to then try installing VS2012 and try VS2013 again to see if it works.
But I really didn't want to waste all that HD space. So I decided to wait until Maxon supported the VS2013 toolset (I think it's vs110?) natively without needing to have 2012 sitting there taking up HD space.

Does this padding issue mean Maxon isn't going to support VS2013 any time in the near future?

-ScottA

On 08/12/2013 at 11:38, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Oh wonderful.Thanks Microsoft. You're the gift that just keeps on giving.  :angry: Does this mean that Maxon is going to be sticking with VS2012 then? I tried compiling the R15 demo with VS2013. But I couldn't, because it required the vs110 toolset that comes with VS2012.I was going to then try installing VS2012 and try VS2013 again to see if it works.But I really didn't want to waste all that HD space. So I decided to wait until Maxon supported the VS2013 toolset (I think it's vs110?) natively without needing to have 2012 sitting there taking up HD space.Does this padding issue mean Maxon isn't going to support VS2013 any time in the near future?-ScottA

I can't give any forward looking statement on behalf of Maxon, but ...

We've to review API (and utility code) very carefully if there are issues with the Intel compiler (that we're using on Windows as it creates faster code than the MS compiler) when 3rd party plugins would utilize the MS 2013 compiler (as most of you would do).

If there are issues, then there won't be support for VS 2013 in the near future.

Best regards,

Wilfried

On 08/12/2013 at 13:43, xxxxxxxx wrote:

Ok thanks.
I get that you're bound to an NDA. But it sure would be nice to know if we're talking months, years, or never when it comes to native VS2013 spport.

Reading between the lines. It's not sounding so good for 2013 support any time soon. :angry:

-ScottA

On 09/12/2013 at 02:04, xxxxxxxx wrote:

What I read between the lines is, that it might be a good idea to use the intel compiler too.