[
https://issues.apache.org/jira/browse/PARQUET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089486#comment-15089486
]
Wes McKinney commented on PARQUET-267:
--------------------------------------
I can look into getting gcc-4.9 working on Travis; sorry about the hassle there.
The trouble with installing thirdparty in the build directory is that there may
be multiple build directories (in the case of out-of-source builds -- this
makes branch-switching less painful) -- but people doing significant
development are probably going to want to set the install locations of all the
dependencies outside of the sandbox.
I agree that maintaining a Thrift build recipe may be onerous (see an example
one here:
https://github.com/cloudera/native-toolchain/blob/master/source/thrift/build.sh).
As long as we have a consistent pattern for configuring each library install
prefix, then that's already a big improvement.
> 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)
