Hi,
Yesterday I downloaded and installed MSVC 2017 Community because I needed a full compatibility with the C++11 standard that I have on *nix/Mac.
The installation went fine.
Next I opened wx_vc15.sln and tried to compile everything (I'm using wx-3.1.0).
Here are the results.
The "Help->About" menu says:
Microsoft Visual Studio Community 2017 Version 15.7.5.
I'm sure that all those are fixed already on Git HEAD, but its not in 3.1.0 yet.
However, I'd rather patch this locally, because I am running patched version of 3.1 on *nix/Mac (hopefully Vadim will find time to review and apply my patches).
Any idea on the fixes?
Thank you.
P.S.: Or maybe I can go to 3.1.1?
Going to MSVC2017
Re: Going to MSVC2017
I'm pretty sure i've built wxWidgets is VS2017 already in the past, but i can't remember which wx version.
Did you "clean" before building?
Can you try building a "static" release (non DLL) for a test (because these are the only ones i ever use, i never build the DLL configuration).
Did you "clean" before building?
Can you try building a "static" release (non DLL) for a test (because these are the only ones i ever use, i never build the DLL configuration).
Use the source, Luke!
Re: Going to MSVC2017
I just tested building wx 3.1.0 with VS2017, no problems with either static or DLL version.
Use the source, Luke!
Re: Going to MSVC2017
MSVC 2017 was released in March 2017. Last commit tagged for wxWidgets 3.1.0 was on Feb 28, 2016, I do not see the solution for VS2017 (wx_vc15.sln) there: https://github.com/wxWidgets/wxWidgets/ ... /build/msw
OTOH, wxWidgets provide prebuilt MSVC 2017 libraries even for 3.04 version (probably built via makefiles), so...
OTOH, wxWidgets provide prebuilt MSVC 2017 libraries even for 3.04 version (probably built via makefiles), so...
Re: Going to MSVC2017
Could it be that you compiled without cleaning older build files, from a different VS?
I find it really, really hard to believe that MS waited until 2017 to have C++11 support..ONEEYEMAN wrote:I downloaded and installed MSVC 2017 Community because I needed a full compatibility with the C++11 standard
Indeed, through what magic did you do that? That file was not there in 3.1.0, which again points to a mixup.ONEEYEMAN wrote:Next I opened wx_vc15.sln and tried to compile everything (I'm using wx-3.1.0).
Whether VS2017 fixes were needed or not, they will never be in 3.1.0 which is merely a code tag. But since 3.1.1 is out for a while now, are there any polemics left to debate?ONEEYEMAN wrote:I'm sure that all those are fixed already on Git HEAD, but its not in 3.1.0 yet.
Re: Going to MSVC2017
Hi,
I am trying to do a clean rebuild right now.
I knew I have 3.1 version - I just forgot which one.
Thank you.
Possible.catalin wrote: Could it be that you compiled without cleaning older build files, from a different VS?
I am trying to do a clean rebuild right now.
Well, I know MSVC 2010 does not have everything, namely thread support. And trying MSVC 2015 (or whatever the previous version was) was kind of inappropriate.catalin wrote:I find it really, really hard to believe that MS waited until 2017 to have C++11 support..ONEEYEMAN wrote: I downloaded and installed MSVC 2017 Community because I needed a full compatibility with the C++11 standard
I guess I'm getting old.catalin wrote:Indeed, through what magic did you do that? That file was not there in 3.1.0, which again points to a mixup.ONEEYEMAN wrote: Next I opened wx_vc15.sln and tried to compile everything (I'm using wx-3.1.0).
I knew I have 3.1 version - I just forgot which one.
We will see how my rebuild will go...catalin wrote:Whether VS2017 fixes were needed or not, they will never be in 3.1.0 which is merely a code tag. But since 3.1.1 is out for a while now, are there any polemics left to debate?ONEEYEMAN wrote: I'm sure that all those are fixed already on Git HEAD, but its not in 3.1.0 yet.
Thank you.