[
https://issues.apache.org/jira/browse/HDFS-11518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410466#comment-16410466
]
Hudson commented on HDFS-11518:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13869 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13869/])
HDFS-11518: libhdfs++: Add a build option to skip building examples,
(james.clampffer: rev 1c9b174663f4f73f7cce275e2d7b302c7d37d293)
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/CMakeLists.txt
> libhdfs++: Add a build option to skip building examples, tests, and tools
> -------------------------------------------------------------------------
>
> Key: HDFS-11518
> URL: https://issues.apache.org/jira/browse/HDFS-11518
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: James Clampffer
> Assignee: Anatoli Shein
> Priority: Major
> Attachments: HDFS-11518.HDFS-8707.000.patch,
> HDFS-11518.HDFS-8707.001.patch, HDFS-11518.HDFS-8707.002.patch
>
>
> Adding a flag to just build the core library without tools, examples, and
> tests will make it easier and lighter weight to embed the libhdfs++ source as
> a third-party component of other projects. It won't need to look for a JDK,
> valgrind, and gmock and won't generate a handful of binaries that might not
> be relevant to other projects during normal use.
> This should also make it a bit easier to wire into other build frameworks
> since there won't be standalone binaries that need the path to other
> libraries like protobuf while the library builds. They just need to be
> around while the project embedding libhdfs++ gets linked.
--
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
