Hi,
It seems Microsoft Visual Studio (Community) 2017 released has been released and is available for download now. It includes MSC14 too. U++ 2017.1 can automatically find and configure that one. However, the MSC15 compiler included is not automatically detected, but can be manually added to U++ build methods. Any plans to support auto detection for that one soon?
Hi cbpporter
If I select Builder without x64 then it is giving linking error.
Any Builder with X64 Linking is working. I want to build for 64 bit system.
********************************************************************** ** Visual Studio 2017 Developer Command Prompt v15.0.26403.7 ** Copyright (c) 2017 Microsoft Corporation ********************************************************************** [vcvarsall.bat] Environment initialized for: 'x64' C:\Program Files (x86)\Microsoft Visual Studio\2017\Community>cl Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25019 for x64 Copyright (C) Microsoft Corporation. All rights reserved. usage: cl [ option... ] filename... [ /link linkoption... ] C:\Program Files (x86)\Microsoft Visual Studio\2017\Community>link Microsoft (R) Incremental Linker Version 14.10.25019.0 Copyright (C) Microsoft Corporation. All rights reserved. usage: LINK [options] [files] [@commandfile]
This all adds up to a very confusing versioning. Would it be clearer to start using the Visual Studio versioning
and call the build methods along the lines of VS2015, VS2017 to keep track of what compiler product to install to get specific build system? Or
would it be better to go along with the version number of the compiler (e.g. 19.10), which is defined with _MSC_VER as e.g. 1910? Anyway, the MSC15 is not correct and I do not feel 14.10 is a strong identifier for the compiler either.
Mirek,
Just out of interest I briefly installed something called "Visual Studio Build Tools 2017".
worked with that too (same as VS2017 Community) at least for 32 bit targets. However, there was no debugger bundled -- or I just could not find
The build method names, in my opinion, should point out the actual toolset installed in a way that it can be easily identified, and therefore found and reinstalled, if needed.
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.10.25017\include\xtr1common(100): error C2737: 'std::is_same_v': 'constexpr' object must be initialized
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.10.25017\include C:\Program Files (x86)\Windows Kits\10\Include\10.0.10586.0\um C:\Program Files (x86)\Windows Kits\10\Include\10.0.10586.0\ucrt C:\Program Files (x86)\Windows Kits\10\Include\10.0.10586.0\shared
Thank you Tom. However in my case TheIDE Automatic Build Setup does not generate any new file.
I have moved all .bm files to other folder, opened TheIDE and called Automatic Build Setup. Then it finds old install 14, but it does not find "Microsoft Visual Studio\2017".
I installed 2017 from here: https://www.visualstudio.com/thank-you-downloading-visual-st udio/?sku=BuildTools&rel=15. Maybe do I need to install anything else?
Hi Koldo,
Not sure if this helps, but I tested the VS2017 BuildTools by duplicating the build method I already had for VS2017 community edition (which was automatically generated by theide). Then I just renamed it and changed the include, lib and bin folders to point at BuildTools instead of the VS community.
Tom
I just took a closer look and found that your MSC17x64.bm file also had PATH and LIB references pointing at VS2017 Community. Only INCLUDE was pointing to BuildTools. This may explain if you had issues with your BM when trying to use BuildTools instead of Community.Thank you Tom, you are right!
c:\program files (x86)\windows kits\10\include\10.0.15063.0\um\winsock2.h (882): fatal error C1083: Cannot open include file: 'qos.h': No such file or directory
PATH = "...;c:/program files (x86)/windows kits/10/bin/x86;...;
PATH = "...;c:/program files (x86)/windows kits/10/bin/x64;...;
Sorry for the delay. Here are the BMs (auto-generated by TheIDE 11218) for Visual Studio 2017 Community and also Visual Studio 2017 Build Tools.
Hi Luigi,
I think you will require this additionally.
https://developer.microsoft.com/en-US/windows/downloads/wind ows-10-sdk
Hi Luigi,
Check your "build methods" settings in MSCxx method
Add in "PATH - executable directories" folder path for "Windows Kits" where rc.exe is located.
In my case it is
"C:\Program Files (x86)\Windows Kits\10\bin\x64"
Add in "PATH - executable directories" folder path for "Windows Kits" where rc.exe is located.
In my case it is
"C:\Program Files (x86)\Windows Kits\10\bin\x64"
The only problem is that I have not found any devenv.exe under Microsoft Visual Studio\2017.
However TheIDE seems to compile and debug