[ARROW-4611] [C++] Rework CMake third-party logic

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.13.0
• Component/s: C++, Packaging
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/21150
• Assignee: Uwe Korn
• Reporter: Uwe Korn
• Created: 18/Feb/19 08:01
• Updated: 11/Jan/23 07:35
• Resolved: 14/Mar/19 15:09

Description

Instead of the current approach we are taking with the *_HOME variables, we should use more CMake features and also give users of Arrow a more high-level control. This is going to be a rather lengthy issue with a lot of subtasks.

• Let the user decide on the top-level how dependencies should be handled. At the moment I can think of the following modes:
  • AUTO: Guess the packaging system we're running in, use this where possible, otherwise build the dependencies through the ExternalProject logic.
  • BUNDLED: Don't use any dependencies, build them all through ExternalProject
  • SYSTEM: Use CMake's find_package and find_library without any custom paths. If packages are on non-default locations, let the user indicate it from the outside using the *_ROOT variables.
  • CONDA: Same as SYSTEM but set all *_ROOT variables to ENV{CONDA_PREFIX}.
  • BREW: This uses SYSTEM but asks brew for some dependencies for their installation prefix.
• prefer dynamic linkage where possible
• Use pkg-config and *Targets.cmake files in projects that publish these
• Ensure that the necessary integration tests are in place (Fedora, Debian, Ubuntu, Alpine)
• Integration tests that Arrow's *Targets.cmake and arrow.pc work.

Issue Links

• contains: ARROW-3486 [CI] Add gandiva to the docker-compose setup
• is a parent of: ARROW-4608 [C++] cmake script assumes that double-conversion installs static libs
• is a parent of: ARROW-4383 [C++] Use the CMake's standard find features
• is a parent of: ARROW-4614 [C++/CI] Activate flight build in ci/docker_build_cpp.sh
• links to: GitHub Pull Request #3688