You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 included. This will be a big easier than maintaining this on an ad hoc basis.
In the C++ build system, we are handling relationships between optional components in an ad hoc fashion
arrow/cpp/CMakeLists.txt
Line 266 in d5ba83e
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.Reporter: Wes McKinney / @wesm
Assignee: Kouhei Sutou / @kou
PRs and other links:
Note: This issue was originally created as ARROW-6858. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: