[
https://issues.apache.org/jira/browse/HADOOP-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209531#comment-16209531
]
Ian Dunlop commented on HADOOP-14667:
-------------------------------------
While building Hadoop 3.0 with Windows 10 VS2017 I did some experimenting and
noticed that with maven you can pass a command line argument in which can be
used inside the pom. I changed the /hadoop-hdfs-project/hadoop-hdfs/pom.xml
line to read
<arg line="${basedir}/src/
-DGENERATED_JAVAH=${project.build.directory}/native/javah
-DJVM_ARCH_DATA_MODEL=${sun.arch.data.model}
-DREQUIRE_LIBWEBHDFS=${require.libwebhdfs} -DREQUIRE_FUSE=${require.fuse} -G
'${vsversion}'"/>
and started mvn with
mvn package -Pdist -Dmaven.javadoc.skip=true -DskipTests -Dtar
"-Dvsversion=Visual Studio 15 2017 Win64"
Here I set the param "vsversion" to "Visual Studio 15 2017 Win64". The quotes
may not be needed - I haven't checked. You can change the VS version to
whatever cmake VS generator you want. One less hard coded parameter. There is
still the issue of updating the VS proj files but at least this is one file
that you would not have to change.
> 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,
> HADOOP-14667.05.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]
