[ARROW-4026] [C++] Use separate modular $COMPONENT-test targets for unit tests

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.12.0
• Component/s: C++
• Labels: pull-request-available
• Assignee: Wes McKinney
• Reporter: Wes McKinney
• Created: 14/Dec/18 04:06
• Updated: 17/Dec/18 21:23
• Resolved: 17/Dec/18 21:23

Description

Because some tests depend on libraries from another component (e.g. "gandiva" relies on "arrow"), if we build "gandiva" and ARROW_BUILD_TESTS=ON then we must also built the tests attached to the "arrow" target. This can be hacked around using the ARROW_TEST_INCLUDE_LABELS option, but the best thing would probably be to create separate modular targets for the unit tests:

• "arrow-tests" depends on "arrow"
• "parquet-tests" depends on "parquet", "arrow"
• "gandiva-test" depends on "gandiva", "arrow"

Issue Links

• links to: GitHub Pull Request #3204