search

microsoft / vscode-cmake-tools

CMake integration in Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=vector-of-bool.cmake-tools
MIT License
1.47k stars 454 forks source link

Visual C++ build tools default display name #289

Closed MathiasMagnus closed 1 month ago

MathiasMagnus commented 6 years ago

Brief Issue Summary

The default display name for MSVC compilers are far too long. Visual Studio Build Tools 2017 - amd64 takes up a lot of space from the status bar.

Expected:

Something shorter.

Suggestion:

I suggest using from vswhere.exe either the "installationVersion": "15.5.27130.2010" or the "productDisplayVersion": "15.5.2" properties as the basis of the version numbers.

With GCC compilers showing as GCC 7.2.0 and Clang compilers showing as Clang 5.0.1, I suggest one of the following:

Perhaps the shorter version numbers are closer to the Clang/GCC versioning scheme.

Platform and Versions

[[For issues, fill out the following. Otherwise delete this section.]]

MathiasMagnus commented 6 years ago

Or as third option, when only the build tools are installed, and there actually is no VS install version to report, it might extract the actual version of the compiler. (Or even when there IS a VS install.)

PS C:\Users\nagy-> cl.exe
Microsoft (R) C/C++ Optimizing Compiler Version 19.12.25831 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

usage: cl [ option... ] filename... [ /link linkoption... ]

The compiler major version for historic reasons is always 4 higher than the corresponding VS major version. When using MSVC, I am primarily interested in the last number, as that allows me to identify which C++ features I can expect.

Anyone else using MSVC or having opinions on these? Knowing which VS version ships the given compiler is nice, though it doesn't help finding out whether online compilers (cloudapp and godbolt) are older/newer than my offline one.