[
https://issues.apache.org/jira/browse/HADOOP-16072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753134#comment-16753134
]
Allen Wittenauer commented on HADOOP-16072:
-------------------------------------------
The reason they are dynamically updated is for forward compatibility. In my
experiences, if the solution files are upgraded to a newer version, older
versions will not be able to build. Changing the minimum compiler version from
VS2010 should probably be discussed with everyone via the mailing list. The
Windows compilers on the ASF Windows boxes are VS2015, IIRC, so going higher
than that version is not an option.
A better solution would be to switch winutils to an entirely cmake driven build
which would generate everything dynamically without the need for solution files
at all. It should have a much better success rate of working with whatever
version is installed and likely a better experience overall.
> Visual Studio projects are out of date
> --------------------------------------
>
> Key: HADOOP-16072
> URL: https://issues.apache.org/jira/browse/HADOOP-16072
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 3.2.0
> Environment: Building on Windows 10 with Visual Studio 2017.
> Reporter: Brian Grunkemeyer
> Assignee: Brian Grunkemeyer
> Priority: Minor
> Labels: build, windows
> Fix For: 3.2.0
>
> Attachments: HADOOP-16072.v1.patch
>
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> On Windows when you build, a part of the build process updates some Visual
> Studio solution and project files. We should simply check in the updated
> version, so that everyone who builds doesn't get stuck with extra changes
> they need to manage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
