Hi Alex, The libs will not be compatible. All versions of MSVC since 2010 write a version string into libs. And all versions since 2012 check this string. You can not link to libs compiled with a older version.
Also I can just repeat myself: We don't want to switch to 2013. I would just like to keep track of the changes and try to keep blenders code compatible with future versions. /Jürgen Am 29.06.2013 um 04:23 schrieb Alexandr Kuznetsov <kuzsa...@gmail.com>: > Hi Jürgen and Thomas: > > From what I understand, they just release the *preview* version of vs > 2013. I would advise to wait for the final release due to possible > incompatibility between this and final versions (libs wise). I don't see > a reason to move to 2013 preview right now. We don't use C++ much and to > the full extend (except possibly Cycles) and I'm not aware of that2013 > brings C11 support. > Also, if you have previous toolkit installed (vs 2012), the 2012 libs > should still be compatible with 2013. When 2013 is released, we can drop > 2012 as we did with 2010. And still have 2008 as official! > As for the patch to the code to make it compliant with c++11, it would > be great addition (although gcc doesn't have issues). > > Best, > Alex > > > On 6/28/2013 6:46 PM, Jürgen Herrmann wrote: >> Hi Thomas, >> >> I don't want to update right now, but as ms changed their pace to yearly >> updates with significant new features and changed compatibilities (e.g more >> c++11 features) we will have to do a lot of work if we wait 5 years again. >> As I said I've got a patch for VS 2013 ready and working in my local repo. >> We could update instantly but I don't want to due to the reasons you stated. >> I just want to avoid the messy update work we had because we skipped one >> version. >> If we skip 5 versions of MSVC (provided that ms keeps this pace) the >> updating mess will be huge :( >> So doing a little testing once and a small patch in a while wont hurt, I >> think. >> >> Am 28.06.2013 um 23:27 schrieb Thomas Dinges <blen...@dingto.org>: >> >>> Hi Jürgen, >>> >>> We used vc2008 now for like 5 years? or so, and this worked out quite >>> good. Probably we should update more frequently, but I see no reason to >>> rush things either. >>> It will still take some weeks or months to test vc2012 with Blender >>> thoroughly, to use this as a vc2008 replacement for official builds. >>> >>> So let's finish the vc2012 update first, use it for official builds and >>> then worry about when and if we should update the next time. ;) >>> >>> Thomas >>> >>> Am 28.06.2013 23:14, schrieb Jürgen Herrmann: >>>> Sure! Switch to MinGw, but please do some good testing ;) >>>> I am the last not to support this ;) >>>> >>>> Am 28.06.2013 um 20:13 schrieb Cezary Kopias <cezary.kop...@gmail.com>: >>>> >>>>> From USER: As always speed tests must be performed for such a decision. >>>>> Are there any new VS features that are worth mention? >>>>> >>>>> And as always i will promote mingw-w64 :] >>>>> just read that you can compile windows build under linux - nice >>>>> >>>>> /kopias >>>>> >>>>> On Fri, 28 Jun 2013 20:08:30 +0200, Jürgen Herrmann <shadow...@me.com> >>>>> wrote: >>>>> >>>>>> Logic error corrected inline ;) >>>>>> >>>>>>> Hi there, >>>>>>> >>>>>>> Out of curiosity I downloaded the VS 2013 Pro preview yesterday. >>>>>>> And while playing with it I had the idea to try blender compilation >>>>>>> with it ;) >>>>>>> I needed to tweak the sources a bit because MSVC 12 seems to break se >>>>>>> things as M$ implements more C++11 features. It took me 30 Minutes to >>>>>>> put a patch together. >>>>>>> But all the libs I compiled with VC11 need to be recompiled :( >>>>>>> So I stopped this insanity ... >>>>>>> >>>>>>> But what I am curious about, what do you guys think? >>>>>>> Shall we adapt new versions if MSVC early (even if we don't use it for >>>>>>> production) or not? >>>>>>> Pro: when we decide to switch to another version (let's assume MSVC >>>>>>> 2016, just for an example) the workload of porting might >>>>>> Not be that huge. >>>>>>> Con: we have to recompile libs and port blender every year (in case MS >>>>>>> keeps this release schedule) >>>>>>> >>>>>>> /Jürgen >>>>>>> _______________________________________________ >>>>>>> Bf-committers mailing list >>>>>>> Bf-committers@blender.org >>>>>>> http://lists.blender.org/mailman/listinfo/bf-committers >>>>>> _______________________________________________ >>>>>> Bf-committers mailing list >>>>>> Bf-committers@blender.org >>>>>> http://lists.blender.org/mailman/listinfo/bf-committers >>>>> -- >>>>> Using Opera's mail client: http://www.opera.com/mail/ >>>>> _______________________________________________ >>>>> Bf-committers mailing list >>>>> Bf-committers@blender.org >>>>> http://lists.blender.org/mailman/listinfo/bf-committers >>>> _______________________________________________ >>>> Bf-committers mailing list >>>> Bf-committers@blender.org >>>> http://lists.blender.org/mailman/listinfo/bf-committers >>> >>> -- >>> Thomas Dinges >>> Blender Developer, Artist and Musician >>> >>> www.dingto.org >>> >>> _______________________________________________ >>> Bf-committers mailing list >>> Bf-committers@blender.org >>> http://lists.blender.org/mailman/listinfo/bf-committers >> _______________________________________________ >> Bf-committers mailing list >> Bf-committers@blender.org >> http://lists.blender.org/mailman/listinfo/bf-committers > > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers