[
https://issues.apache.org/jira/browse/HDFS-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Clampffer updated HDFS-13362:
-----------------------------------
Description:
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?
was:
libhdfs++ has significantly increased 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?
> 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
>
> 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
