Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » Coffee corner » Visual Studio (Community) 2017 released
Visual Studio (Community) 2017 released [message #47733] Wed, 15 March 2017 15:11 Go to next message
Tom1
Messages: 377
Registered: March 2007
Senior Member
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?

I must admit that installation and configuration of VS2017 (for desktop application workload) was easier than before.

Best regards,

Tom
Re: Visual Studio (Community) 2017 released [message #47736 is a reply to message #47733] Thu, 16 March 2017 19:20 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 11082
Registered: November 2005
Ultimate Member
Tom1 wrote on Wed, 15 March 2017 15:11
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?


Definitely!

I am thinking that next release should be 2-3 months away. Will probably contain Debian 9 compatibility fixes, this one, and some GIT support.

Mirek
Re: Visual Studio (Community) 2017 released [message #47777 is a reply to message #47733] Sat, 25 March 2017 05:30 Go to previous messageGo to next message
deep is currently offline  deep
Messages: 179
Registered: July 2011
Location: Bangalore
Experienced Member
Hi

Have anyone installed VS2017 Community.
I need BM file.

I have installed VS2017 community. Install dir is not in C:. UPP is not finding it automatically. Also I have MinGW in other drive. It is also not auto detected. but could set up manually by copying BM file from other location and modifying it.

Can some one share BM file for VS2015 or VS2017.


Warm Regards

Deepak

[Updated on: Sat, 25 March 2017 05:43]

Report message to a moderator

Re: Visual Studio (Community) 2017 released [message #47794 is a reply to message #47777] Mon, 27 March 2017 08:51 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1274
Registered: September 2007
Senior Veteran
Sorry, don't have one for 15. I attached the 14 one, don't know if it will help.

But I never bothered with BM files.

I use the build method navigator and if I point TheIDE in the right direction, I can make it work with any version, probably VS2017 to.

Try something like:
c:/program files (x86)/microsoft visual studio 15.0/
c:/program files (x86)/windows kits/10/lib/

Basically the latest version of VS and Windows Kits.

I have my own detection code, so I guess I need to update it for VS2017.



  • Attachment: MSC14.bm
    (Size: 1.18KB, Downloaded 23 times)
Re: Visual Studio (Community) 2017 released [message #47795 is a reply to message #47794] Mon, 27 March 2017 10:46 Go to previous messageGo to next message
deep is currently offline  deep
Messages: 179
Registered: July 2011
Location: Bangalore
Experienced Member
Hi cbpporter

Thank you for your file.

Now I have generated MSC17.bm file.

But one strange thing happening.

if Builder name not available in dropdown of build methods it gives invalid builder.
So I selected MSC15X64. All other relevant files for VS2017 selected. It is working.

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.

BUILDER selected from droplist is changing some flag for linking.

BUILDER = "MSC15X64";


My working MSC17.bm

Any suggestions for the options in .bm file
  • Attachment: MSC17.bm
    (Size: 1.44KB, Downloaded 33 times)


Warm Regards

Deepak

[Updated on: Mon, 27 March 2017 10:48]

Report message to a moderator

Re: Visual Studio (Community) 2017 released [message #47796 is a reply to message #47795] Wed, 29 March 2017 09:23 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1274
Registered: September 2007
Senior Veteran
Well, I'll get back to you when I get to install the latest VS. This will take at least one month. I have two post release bi-weekly updates to prepare so I have no time to install new VS. When I'll install I'll also test auto-detecting it.

Until then, as Mirek said, we might get official support for auto-detection. If you managed to get it to work with that BM file it means that the process is similar to the rest of MSC so auto-detection should be easy.

Re: Visual Studio (Community) 2017 released [message #47811 is a reply to message #47795] Sun, 02 April 2017 00:52 Go to previous messageGo to next message
wimpie is currently offline  wimpie
Messages: 31
Registered: March 2013
Location: holland
Member
deep wrote on Mon, 27 March 2017 10:46
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.


my thanks also. "Builder without x64" needs other paths.. to x86 stuff.
I just installed UPP after some time, and installed VS community 2017 also, and tried your BM file after some path adjustments.

next thing to try... clang/c2???


  • Attachment: MSC17.bm
    (Size: 1.43KB, Downloaded 27 times)
Re: Visual Studio (Community) 2017 released [message #48417 is a reply to message #47736] Mon, 03 July 2017 12:40 Go to previous messageGo to next message
Tom1
Messages: 377
Registered: March 2007
Senior Member
Hi,

It seems the Microsoft Visual C++ compilers' version naming on U++ is not entirely accurate. For quite a while U++ used MSC15 for what is now called MSC14. Later, on top of this thread I made a mistake by calling the new compiler version MSC15. Well, according to this, it was a mistake:

https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B#Inter nal_version_numbering

This sort of implies we should have used MSC14.1 for the VS 2017 compiler. Or maybe we should have used MSC19.1 instead: Namely, when we open the VS 2017 64-bit build environment and call cl.exe and link.exe we will get:

**********************************************************************
** 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]


So, in effect we have compiler version 19.10 and linker version 14.10 running on top of Developer command prompt 15.0...

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.

Best regards,

Tom

[Updated on: Mon, 03 July 2017 12:40]

Report message to a moderator

Re: Visual Studio (Community) 2017 released [message #48419 is a reply to message #48417] Mon, 03 July 2017 14:54 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 11082
Registered: November 2005
Ultimate Member
Tom1 wrote on Mon, 03 July 2017 12:40

This all adds up to a very confusing versioning. Would it be clearer to start using the Visual Studio versioning


Well, that is why I was using MSC15 initially... (but the community did not liked that...)

Quote:

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


Might work. I was a little bit hesitant to have "VS" moniker, as we are using just compiler.

Quote:

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.


Another option is to keep MSC14 for 2017 too - in reality, if I remember well, nothing has changed except autodetection process...

Best regards,

Tom[/quote]
Re: Visual Studio (Community) 2017 released [message #48421 is a reply to message #48419] Mon, 03 July 2017 15:26 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1274
Registered: September 2007
Senior Veteran
Visual Studio 2015 = MSC14 = CL 19.00
Visual Studio 2017 = MSC15 = CL 19.10

Tom1, is this not what you expect to see?
Re: Visual Studio (Community) 2017 released [message #48422 is a reply to message #48419] Mon, 03 July 2017 15:32 Go to previous messageGo to next message
Tom1
Messages: 377
Registered: March 2007
Senior Member
Mirek,

Just out of interest I briefly installed something called "Visual Studio Build Tools 2017". The idea was to drop out the VS IDE. After manually adjusting the paths (auto detection does not work for this), the compilation and linking 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 it. Anyway, I removed it and reinstalled VS2017 Community. The reason for trying was to avoid the unnecessarily large installation of the whole VS2017.

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.

--

cbpporter: MSC15 was what I expected to see, before I found the link and thereafter some other material pointing out that it might actually be MSC14.1. Indeed the toolset referred by the Visual Studio 2017 installer refers to v141 for the latest toolset.

I just wanted to point out that I may have made a mistake by assuming it would have been version 15 whereas it may have been 14.1 in question.

Best regards,

Tom
Re: Visual Studio (Community) 2017 released [message #48423 is a reply to message #48422] Mon, 03 July 2017 15:36 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1274
Registered: September 2007
Senior Veteran
14.1 is not something I can find in the main listing.

Might it be related to the pre-release version? I think it is a RC or something.
Re: Visual Studio (Community) 2017 released [message #48425 is a reply to message #48423] Mon, 03 July 2017 16:11 Go to previous messageGo to next message
Tom1
Messages: 377
Registered: March 2007
Senior Member
You see the link below. It is 14.1 there:

https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B#Inter nal_version_numbering

Additionally, when you run Visual Studio 2017 installer and select Visual Studio Community 2017 and Desktop development with C++ workload, you can see "VC++ 2017 v141 toolset (x86,x64)" as a selected component. Further on, there is an option to install "VC++ 2015.3 v140 toolset (x86,x64)".

When you search the web for microsoft visual c++ compiler versions, you will find additional discussions of the confusion over the version numbers.

I started this discussion here for U++ users to recognize the problem and possibly overcome the current situation by changing the naming to something that easily relates to the Microsoft compiler product being used. For me personally, it does not matter what they are called as far as I know what to install and that the result will work correctly. However, to avoid confusion and therefore wasted time for many other people, it would be easier to use names and numbers that can be used to pick up a specific compiler product on the web.

Best regards,

Tom

[Updated on: Mon, 03 July 2017 16:13]

Report message to a moderator

Re: Visual Studio (Community) 2017 released [message #48427 is a reply to message #48425] Mon, 03 July 2017 16:21 Go to previous messageGo to next message
Tom1
Messages: 377
Registered: March 2007
Senior Member
Hi,

Please take into account the possibility that Microsoft too is confused here; Microsoft VC CRT redistributable components are in a folder called Microsoft.VC150.CRT but contain files with names *140.dll ...

Best regards,

Tom
Re: Visual Studio (Community) 2017 released [message #48429 is a reply to message #48422] Mon, 03 July 2017 17:40 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 11082
Registered: November 2005
Ultimate Member
Tom1 wrote on Mon, 03 July 2017 15:32
Mirek,

Just out of interest I briefly installed something called "Visual Studio Build Tools 2017".


Do they release this once again? Cool! Where is the link?

Quote:

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


Debugger in theide is sort of independent of it, as long as build tools are able to produce debug info / .pdb.

Quote:

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.


Personally, I would prefer MSCyear scheme. It is really unlikely that they would change compiler commandline options twice in single year and with all the confusion about MSC version it is as good as it gets. That would make current MSC: MSC17.

BTW:

https://blogs.msdn.microsoft.com/vcblog/2016/11/16/introduci ng-the-visual-studio-build-tools/

It seems like MS 'screenname' is VC++ 2017 v141, which is inline with MSC17 (IMO).
Re: Visual Studio (Community) 2017 released [message #48432 is a reply to message #48429] Mon, 03 July 2017 20:51 Go to previous messageGo to next message
Tom1
Messages: 377
Registered: March 2007
Senior Member
Mirek,

I installed Visual Studio 2017 build tools using this link:

https://www.visualstudio.com/thank-you-downloading-visual-st udio/?sku=BuildTools&rel=15

Visual Studio 2015 build tools download button can be found on:

http://landinghub.visualstudio.com/visual-cpp-build-tools

MSCyear would be fine with me. However, since the convention would then change from what it was until now, should it use four digit year instead? Like MSC2017 to reflect the fact that the logic has changed and it is no longer the toolset version that is being referred to by the number.

If you look at the Visual Studio installation folders' names in C:\Program Files (x86)\ carefully, you can see that the old ones used to be like "Microsoft Visual Studio 9.0" and "Microsoft Visual Studio 14.0". But now for the first time it is just "Microsoft Visual Studio" and now there is a sub folder called "2017".

Best regards,

Tom
Re: Visual Studio (Community) 2017 released [message #48444 is a reply to message #48432] Tue, 04 July 2017 11:26 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 2757
Registered: August 2008
Location: Basque Country
Senior Veteran
Hello all

After installing MSVC, I have created a MSC17x64.bm file based in MSC17.bm file uploaded in this post.

I get these errors:
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

Include folders are:
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


Best regards
Koldo
Re: Visual Studio (Community) 2017 released [message #48450 is a reply to message #48444] Tue, 04 July 2017 12:47 Go to previous messageGo to next message
Tom1
Messages: 377
Registered: March 2007
Senior Member
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.

Best regards,

Tom
Re: Visual Studio (Community) 2017 released [message #48462 is a reply to message #48450] Wed, 05 July 2017 16:16 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 2757
Registered: August 2008
Location: Basque Country
Senior Veteran
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?


Best regards
Koldo
Re: Visual Studio (Community) 2017 released [message #48464 is a reply to message #48462] Wed, 05 July 2017 18:31 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 11082
Registered: November 2005
Ultimate Member
koldo wrote on Wed, 05 July 2017 16:16
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?


Are you using U++ trunk version?

(Current stable was released about the same time as VS2017, so there is not a support in stable yet).
Previous Topic: Web Assembly... Compiling U++ code to run in the web browser...
Goto Forum:
  


Current Time: Fri Aug 18 03:17:41 CEST 2017

Total time taken to generate the page: 0.00715 seconds