-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[tools] Visual Studio 2017 (15.2) required #5
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
|
||
# Proposal: Tools - Visual Studio 2017 (15.2) required | ||
|
||
| **Status** | **Proposed/Accepted/Deprecated** | | ||
|:------------------|:---------------------------------------------| | ||
| **RFC #** | #### | | ||
| **Submitted** | YYYY-MM-DD | | ||
| **Dependencies** | RFC #, # | | ||
|
||
--- | ||
|
||
## Summary | ||
Declare **Microsoft Visual Studio 2017 (15.2)** as the minimal version supported. | ||
|
||
|
||
## Motivation | ||
Visual Studio 2017 (15.2) was [released on May 2017](https://docs.microsoft.com/visualstudio/releasenotes/vs2017-relnotes-v15.2). This version allows to install | ||
side-by-side different versions of the MSVC toolset, it allows you to [build binaries | ||
that are fully compatible with the ones built using older versions](https://devblogs.microsoft.com/cppblog/stuck-on-an-older-toolset-version-move-to-visual-studio-2015-without-upgrading-your-toolset/). | ||
|
||
Visual Studio 2017 (15.2) includes [`wswhere` application](https://github.com/microsoft/vswhere). | ||
This tool is needed Conan to locate Visual Studio installation and toolsets available (link to proposal required). | ||
|
||
|
||
## Proposal | ||
Declare **Visual Studio 2017 (15.2)** as the minimal version supported. | ||
|
||
|
||
## Alternative Approaches | ||
Conan migth need Visual Studio 2017 (15.2) **installed**, but it can target older | ||
jgsogo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
versions (`vswhere` is able to find older installations too). | ||
|
||
|
||
## Detailed Design | ||
|
||
|
||
## Open issues | ||
* Evidence of CLI changes (calling MSBuild or other tools), format changes | ||
in the `.props` files or the data available to them (used in Conan generators | ||
and toolchains). Besides locating the installation, is there any reason not to | ||
support older versions? | ||
|
||
* MSBuild doesn't support long paths until version 16.0 ([link](https://github.com/dotnet/msbuild/issues/53#issuecomment-459062618)). | ||
|
||
|
||
## Future Extensions |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to fix that typo here,
wswhere
->vswhere
but the repo jgsogo:proposal does not exist (for me) , so I do not know how or where to submit the pr for the pr :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now the repository should be public