[
https://issues.apache.org/jira/browse/HADOOP-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109299#comment-16109299
]
Allen Wittenauer commented on HADOOP-14667:
-------------------------------------------
bq. there's bits and pieces of the codebase where those native libs are used in
clientside, even for things like raw local FS, I believe.
You are correct. I've been digging into the unit test failures on the ASF
Windows machines and this is definitely true.
Speaking of: the biggest killers I have right now are HADOOP-14696, HDFS-12220,
YARN-4950, and MAPREDUCE-6674. Running without parallel-tests is just a
non-starter. Unit tests on Linux with parallel are 8 hours. Unit tests on
Windows with HDFS and Common not running/failing over 1000 tests clocks in at
12 hours!
bq. We could look at MSBuild only, and so bypass the need to have VS itself.
Given what I'm seeing with libhdfs, I'm honestly more inclined to think that
the longer term strategy should really be CMake based. There's some really big
benefits:
* one build tool for all of the native code, regardless of platform
* We already have requirements for CMake for Windows
* CMake will build for any version of NMake and VS
*
https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-studio/
But that's a discussion for a different day. I definitely view this patch as a
stop-gap.
> Flexible Visual Studio support
> ------------------------------
>
> Key: HADOOP-14667
> URL: https://issues.apache.org/jira/browse/HADOOP-14667
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.0.0-beta1
> Environment: Windows
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Attachments: HADOOP-14667.00.patch, HADOOP-14667.01.patch,
> HADOOP-14667.02.patch, HADOOP-14667.03.patch, HADOOP-14667.04.patch
>
>
> Is it time to upgrade the Windows native project files to use something more
> modern than Visual Studio 2010?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
