[
https://issues.apache.org/jira/browse/PARQUET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089650#comment-15089650
]
Kalon Mills commented on PARQUET-267:
-------------------------------------
No worries about gcc-4.9. I was trying to do too much as once, so it may have
been a compounding set of problems.
Ah so that's what native-toolchain is. That's pretty nice. With the changes
I've made to the build config it would be easy to set up a build that points to
a native-toolchain initialized build dir.
Is it good enough to just have instructions for setting up dependencies through
native-toolchain and not maintain build recipes here? Or is it better to have
build recipes specific to this repo?
> 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)
