Still looks somewhat risky to me. Unless VS2017 uses C++ standard library implementation from VS2015's "msvcp140.dll", of course.
On 02/24/2017 12:44 PM, Tom Isaacson wrote: > I had the prebuilt VS2015 libraries downloaded and installed and I was able > to rebuild and run our app in VS2017. I didn't have to rebuild Qt myself. > > > Tom Isaacson > > -----Original Message----- > From: Interest > [mailto:interest-bounces+tom.isaacson=navico....@qt-project.org] On Behalf Of > Harri Porten > Sent: Friday, 24 February 2017 20:30 > To: interest@qt-project.org > Subject: Re: [Interest] Support for Visual Studio 2017 > > On Thu, 23 Feb 2017, Tom Isaacson wrote: > >> It worked for me; I was able to run our VS2015 app in VS2017 with no >> problems. > > I think Thiago meant something different: what if you are compiling your > application with VS 2017 against a set of Qt libraries build with VS 2015? > If that works flawlessly a big upgrade pain of the past would be gone. > > Harri.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
