Alexey Serbin created KUDU-3788:
-----------------------------------

             Summary: Allow fethcing and using pre-built 3rd-party components 
when building Kudu
                 Key: KUDU-3788
                 URL: https://issues.apache.org/jira/browse/KUDU-3788
             Project: Kudu
          Issue Type: Improvement
            Reporter: Alexey Serbin


It would be nice to allow to fetch and use pre-built 3rd-party components when 
building Kudu.  Each of the 3rd-party components should be checked against a 
presence of pre-built version that matches the machine architecture and OS, and 
the matching rule should compare at least the following attributes:
* Component name (e.g., gflags)
* Component version (minor, major, patch, or just source hash if no semantic 
versioning is available)
* The machine's CPU architecture that binaries/libraries are built for (e.g., 
x86_64, arm64)
* OS name or flavor/distro name if applicable (e.g., macOS, Ubuntu, Debian, 
RHEL, etc.)
* OS version: major, minor (e.g., 9.1 for RHEL, 24.04 for Ubuntu, 15.7 for 
macOS, etc.)
* The toolchain that the bits are built with: compiler name, major and minor 
versions, and the standard C++ library flavor where applicable (e.g., 
gcc-10.5-libstdc++, clang-15.0)
* Sanitizer option: TSAN if built with tread sanitizer support, or none if a 
regular build



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to