[
https://issues.apache.org/jira/browse/PARQUET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089830#comment-15089830
]
Kalon Mills commented on PARQUET-267:
-------------------------------------
So it looks like native-toolchain doesn't build individual packages on mac so
leveraging that isn't doable for my dev env. However I had another alternative
thought. I think the instructions could go something like this.
# create a build directory
# cd <build-dir>
# cp -r <source-dir>/thirdparty .
# ./thirdparty/download_thirdparty.sh
# ./thirdparty/build_thirdparty.sh
# THRIFT_HOME=$PWD/thirdparty/installed SNAPPY_HOME=$PWD/thirdparty/installed
LZ4_HOME=$PWD/thirdparty/installed cmake <source_dir>
# make
This could also be thrown into a script which takes <build-dir> as a parameter.
This puts all of the thirdparty libraries right in the build dir so that build
envs can be independent in which libraries they use.
Here we still maintain build recipes but that can evolve over time as support
for more envs is requested. (It might also be nice to eventually separate the
build recipes like done in native-toolchain.)
> Relax Third Party Dependency Restrictions
> -----------------------------------------
>
> Key: PARQUET-267
> URL: https://issues.apache.org/jira/browse/PARQUET-267
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-cpp
> Reporter: Kalon Mills
> Priority: Minor
>
> The existing repo has source code for third party dependencies checked into
> the repo. The build system expects those dependencies in a certain place.
> This enforces that the built library conform to those exact dependencies
> without customization.
> Managing third party dependencies is better handled through a build
> environment. It allows the library builder more flexibility over dependency
> versions and locations. It also cleans up the repo from this third party
> code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
