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

James Clampffer commented on HDFS-13362:
----------------------------------------

Attached a patch to turn the build off by passing 
-Dnative_cmake_args="-DSKIP_LIBHDFSPP_BUILD=TRUE" to maven.  Someone who knows 
the maven/ant side of things could most likely add a more explicit maven flag 
pretty easily.

[~jlowe] I think the current build method wasn't a deliberate choice as much as 
it was something that worked well enough so it never got much attention.  
libhdfs++ used to support parallel compilation but since that was never 
integrated into the maven build some dependency issues crept in.  Getting 
parallel builds going again would be really nice and might make the option to 
skip the build unnecessary.  I hadn't attempted that because I wasn't sure 
where to get a default number of build threads to use.  I can take a look at 
fixing the dependency declarations.

> add a flag to skip the libhdfs++ build
> --------------------------------------
>
>                 Key: HDFS-13362
>                 URL: https://issues.apache.org/jira/browse/HDFS-13362
>             Project: Hadoop HDFS
>          Issue Type: Task
>            Reporter: James Clampffer
>            Priority: Minor
>         Attachments: HDFS-13362.000.patch
>
>
> libhdfs++ has significantly increased clean build times for the native client 
> on trunk.  This covers adding a flag that would let people build libhdfs 
> without all of libhdfs++ if they don't need it; it should be built by default 
> to maintain compatibility with as many environments as possible.
> Some thoughts:
> -The increase in compile time only impacts clean builds.  Incremental 
> rebuilds aren't significantly more expensive than they used to be if the code 
> hasn't changed.
> -Compile times for libhdfs++ can most likely be reduced but that's a longer 
> term project.  boost::asio and tr1::optional are header-only libraries that 
> are heavily templated so every compilation unit that includes them has to do 
> a lot of parsing.
> Is it common to do completely clean builds frequently for interactive users?  
> Are there opinions on what would be an acceptable compilation time?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to