That would be this one, https://msdn.microsoft.com/en-us/library/gg154234.aspx
btw, i would assume the use of the newer libstdc++ if i got it right, as that one comes from the sdk too. But maybe i am wrong, didn't gave this a lot of time yet, which is why i couldn't test it yet. -- Björn Breitmeyer | bjoern.breitme...@kdab.com | Senior Software Engineer KDAB (Deutschland) GmbH&Co KG, a KDAB Group company Germany: +49-30-521325470, Sweden (HQ): +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions Am Donnerstag, 18. Juni 2015, 11:00:30 schrieb Gunnar Roth: > Hi Björn, > what is "the knowledgebase article"? Would you mind to share a link? > > And even if there would be a v18.00 compiler, what about the standard c++ > library (headers, libs and dlls) where do they come from? Or would then a > mix of newer compiler and older std c++ libary be used? That could be quite > problematic haven such a mix leading to unpredictable behaviour from a > programmers view. Qt could then not say, vs2013 is the base, but only > vs2013 compiler with vs12012 std libary. Sound crazy... > Regards, > Gunnar > > > > Gesendet: Donnerstag, 18. Juni 2015 um 10:41 Uhr > Von: "Björn Breitmeyer" <bjoern.breitme...@kdab.com> > An: development@qt-project.org > Cc: "Gunnar Roth" <gunnar.r...@gmx.de>, "Thiago Macieira" > <thiago.macie...@intel.com> Betreff: Re: [Development] QtCS: Long Term > Release discussion > Hello Gunnar, > > i still hadn't time to verify this, but. There is a platform builder for > WEC2013, if you generate the SDk with that one it should have the Visual > Studio 2013 compiler, at least thats how i read the knowledgebase article. > Its on my TODO list to verify this, but i still didn't had the time to do > so. > > Best regards > Björn Breitmeyer > > -- > Björn Breitmeyer | bjoern.breitme...@kdab.com | Senior Software Engineer > KDAB (Deutschland) GmbH&Co KG, a KDAB Group company > Germany: +49-30-521325470, Sweden (HQ): +46-563-540090 > KDAB - Qt Experts - Platform-independent software solutions > > Am Donnerstag, 18. Juni 2015, 10:16:49 schrieb Gunnar Roth: > > Gesendet: Donnerstag, 18. Juni 2015 um 08:43 Uhr > > Von: "Thiago Macieira" <thiago.macie...@intel.com> > > An: development@qt-project.org > > Betreff: Re: [Development] QtCS: Long Term Release discussion > > > > On Thursday 18 June 2015 08:23:52 Gunnar Roth wrote: > > > > Am 17.06.2015 um 22:35 schrieb Thiago Macieira > > > > > > > > <thiago.macie...@intel.com>: > > >> > On Wednesday 17 June 2015 19:30:25 Gunnar Roth wrote: > > >> >> Yes that would make us (as a commercial user using a self made port > > >> >> of > > >> >> qt > > >> >> 5.4.1 to wec2013 ) very unhappy. This means 5.6 will be the last > > >> >> version > > >> >> wec2013 would be supported and you would go straight to making a > > >> >> back > > >> >> port > > >> >> very hard or even impossible. > > >> > > > >> > WEC 2013 was never considered deprecated. The deprecation applies to > > >> > WEC 7 > > >> > only. > > >> > > >> Well ok, but how does Lars Knoll’s sentence "we could make > > >> VS2013 the compiler baseline for 5.7.“ fit into this? As the only > > >> supported > > >> compiler for wec2013 is a cl with v 17.00 aka vs2012. > > > > > >Apparently VS2013 can also be used for WEC2013. > > > > IDE: yes > > Compiler: No > > > > This was recently confirmed to as by microsoft. The used compiler comes > > from the platfrombuilder wince800 tree, which is independent from the > > used IDE. The sdk wec2013 compiler form wec2013 qfe M08 has this version: > > Microsoft (R) C/C++ Optimizing Compiler Version 17.00.50728.6 for ARM > > > > the vs2012 arm compiler ( which is meant for win pohne and winrt) has : > > Microsoft (R) C/C++ Optimizing Compiler Version 17.00.61030 for ARM > > > > I don't think the possible usage of the vs2013 ide has any impact on qt > > development. > > Regards, > > Gunnar > > > > > > > > _______________________________________________ > > Development mailing list > > Development@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/development
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development