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.