[
https://issues.apache.org/jira/browse/HDFS-9325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bob Hansen updated HDFS-9325:
-----------------------------
Summary: Allow the location of hadoop source tree resources to be passed to
CMake during a build. (was: Allow the location of hdfs.h to be passed to CMake
during a build.)
As the project grows, we're finding more and more resources that need to be
brought in from various parts of the hadoop source tree (the default config
files are being added to the list in HDFS-9538).
Might I recommend as a solution a two-step approach for CMake:
1) Gather all of the resources (proto files, header files, xml files) that
libhdfs++ needs into a single directory in the output
2) Point the CMake steps to that directory for building
This will make distributing the source tarball for libhdfs++ easier, also. We
can tar up the outputs along with the source and our consumers will have all of
the files they need.
> Allow the location of hadoop source tree resources to be passed to CMake
> during a build.
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-9325
> URL: https://issues.apache.org/jira/browse/HDFS-9325
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: James Clampffer
> Assignee: James Clampffer
>
> It would be nice if CMake could take an optional parameter with the location
> of hdfs.h that typically lives at libhdfs/includes/hdfs/hdfs.h, otherwise it
> would default to this location. This would be useful for projects using
> libhdfs++ that gather headers defining library APIs in a single location.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
