The platform toolset is v141, the one provided with 2017, and the one which the applications are compiled with.
Windows SDK is 10.0.16299.0, the latest available (but the problem is identical with 8.5)
Again, nmake builds wxWidgets within the Visual Studio command prompt, which is tuned to the context of VS, so that all the includes are done with no problems.
Maybe file a bug for .sln?
Link errors with Trunk Topic is solved
Re: Link errors with Trunk
Hi,
Can you reproduce it with 3.1.1?
Thank you.
Can you reproduce it with 3.1.1?
Thank you.
-
- Super wx Problem Solver
- Posts: 488
- Joined: Fri Oct 27, 2006 4:35 pm
- Location: Paris, France
- Contact:
Re: Link errors with Trunk
Some more information:
I deleted wxWidgets and uninstalled Visual Studio Community 2017.
I cloned a fresh wxWidgets.
I (unwittingly) installed Visual Studio Enterprise 2017.
With the same environment (v141 & SDK 10.0.16299.0) same problem, the system files (stddef.h, stdio.h, stdlib.h, fcntl.h, etc) are not found.
@ONEEYEMAN : what do you mean by 3.1.1? if it is the Trunk, then this is the problem I am posting.
Building wxWidgets-3.0.3 with wx_vc12.sln is OK.
Building wxWidgets-3.1.0 with wx_vc14.sln is OK.
I did notice that while VS was preparing the solution for wx_vc15.sln, SDK 8.1 showed up at some point.
Retargeting the solution to 10.0.16299.0 finally solved the problem.
I'll post a bug to that effect, to complete the install.txt file for msw.
I deleted wxWidgets and uninstalled Visual Studio Community 2017.
I cloned a fresh wxWidgets.
I (unwittingly) installed Visual Studio Enterprise 2017.
With the same environment (v141 & SDK 10.0.16299.0) same problem, the system files (stddef.h, stdio.h, stdlib.h, fcntl.h, etc) are not found.
@ONEEYEMAN : what do you mean by 3.1.1? if it is the Trunk, then this is the problem I am posting.
Building wxWidgets-3.0.3 with wx_vc12.sln is OK.
Building wxWidgets-3.1.0 with wx_vc14.sln is OK.
I did notice that while VS was preparing the solution for wx_vc15.sln, SDK 8.1 showed up at some point.
Retargeting the solution to 10.0.16299.0 finally solved the problem.
I'll post a bug to that effect, to complete the install.txt file for msw.
Re: Link errors with Trunk
I have to admit I fail to see a bug there.
You either need to install the required SDK version or retarget the solution to use the SDK version of your choice.
You either need to install the required SDK version or retarget the solution to use the SDK version of your choice.
-
- Super wx Problem Solver
- Posts: 488
- Joined: Fri Oct 27, 2006 4:35 pm
- Location: Paris, France
- Contact:
Re: Link errors with Trunk
Effectively, there is no software bug but I suggested that the documentation should include "Make sure that the project is targeted to the SDK used by Visual Studio." Why waste people's time searching for a non-bug?
Re: Link errors with Trunk
Hi,
I'm not sure what you mean.
The default wx projects/solution have the appropriate SDK defaults. There is no guarantee that the user will install some other SDK.
But independently of this - check the ticket 18075.
Thank you.
I'm not sure what you mean.
The default wx projects/solution have the appropriate SDK defaults. There is no guarantee that the user will install some other SDK.
But independently of this - check the ticket 18075.
Thank you.
-
- Super wx Problem Solver
- Posts: 488
- Joined: Fri Oct 27, 2006 4:35 pm
- Location: Paris, France
- Contact:
Re: Link errors with Trunk
I dont quite see what you mean by 'appropriate SDK defaults'.
When VS2017 is installed, SDK 10.0.16299.0 is the current default. With this default SDK, unless the project wx_vc15.sln is retargeted to 10.0.16299.0 the build fails, as exposed in this post.
When VS2017 is installed, SDK 10.0.16299.0 is the current default. With this default SDK, unless the project wx_vc15.sln is retargeted to 10.0.16299.0 the build fails, as exposed in this post.