[ 
https://issues.apache.org/jira/browse/HADOOP-18506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622741#comment-17622741
 ] 

ASF GitHub Bot commented on HADOOP-18506:
-----------------------------------------

GauthamBanasandra commented on code in PR #5066:
URL: https://github.com/apache/hadoop/pull/5066#discussion_r1002660030


##########
BUILDING.txt:
##########
@@ -540,6 +564,11 @@ configure the bit-ness of the build, and set several 
optional components.
 Several tests require that the user must have the Create Symbolic Links
 privilege.
 
+To simplify the installation of Boost, Protocol buffers, OpenSSL and Zlib 
dependencies we can use
+vcpkg (https://github.com/Microsoft/vcpkg.git). Upon cloning the vcpkg repo, 
checkout the commit
+7ffa425e1db8b0c3edf9c50f2f3a0f25a324541d to get the required versions of the 
dependencies

Review Comment:
   > Why not a specific branch or latest?
   I couldn't find a branch/release in vcpkg where all these dependencies are 
at the required versions.
   
   > It would also be good to add the command.
   Done.





> Update build instructions for Windows using VS2019
> --------------------------------------------------
>
>                 Key: HADOOP-18506
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18506
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build, documentation
>    Affects Versions: 3.4.0
>         Environment: Windows 10
>            Reporter: Gautham Banasandra
>            Assignee: Gautham Banasandra
>            Priority: Major
>              Labels: pull-request-available
>
> With HADOOP-18133, we're finally able to build Hadoop on Windows using Visual 
> Studio 2019. We now need to update the documentation with the latest 
> instructions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to