[
https://issues.apache.org/jira/browse/ARROW-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kouhei Sutou updated ARROW-6858:
--------------------------------
Description:
In the C++ build system, we are handling relationships between optional
components in an ad hoc fashion
https://github.com/apache/arrow/blob/d5ba83eebfaf0652ff5f96f943a3d99d5de96dd2/cpp/CMakeLists.txt#L266
This doesn't seem ideal.
As discussed on the mailing list, I suggest declaring dependencies in a Python
data structure and then generating and checking in a .cmake file that can be
{{include}}d. This will be a big easier than maintaining this on an ad hoc
basis.
was:
In the C++ build system, we are handling relationships between optional
components in an ad hoc fashion
https://github.com/apache/arrow/blob/master/cpp/CMakeLists.txt#L266
This doesn't seem ideal.
As discussed on the mailing list, I suggest declaring dependencies in a Python
data structure and then generating and checking in a .cmake file that can be
{{include}}d. This will be a big easier than maintaining this on an ad hoc
basis.
> [C++] Create Python script to handle transitive component dependencies
> ----------------------------------------------------------------------
>
> Key: ARROW-6858
> URL: https://issues.apache.org/jira/browse/ARROW-6858
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Wes McKinney
> Priority: Major
>
> In the C++ build system, we are handling relationships between optional
> components in an ad hoc fashion
> https://github.com/apache/arrow/blob/d5ba83eebfaf0652ff5f96f943a3d99d5de96dd2/cpp/CMakeLists.txt#L266
> This doesn't seem ideal.
> As discussed on the mailing list, I suggest declaring dependencies in a
> Python data structure and then generating and checking in a .cmake file that
> can be {{include}}d. This will be a big easier than maintaining this on an ad
> hoc basis.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
