DylanLukes commented on issue #38338: URL: https://github.com/apache/arrow/issues/38338#issuecomment-1771449939
> Although in the case of pyarrow, when it's building against an Arrow C++ build that already made such choices, it might be nice to automatically infer whatever is supported by libarrow (if you build both from source that is certainly possible, not sure if that would also work when building against a brew-installed Arrow C++) Agreed. And it should be easy enough actually. The file `/opt/homebrew/Cellar/apache-arrow/13.0.0_8/lib/cmake/Arrow/ArrowOptions.cmake` contains the options used for Brew's build (which is from source): ```cmake ... ## Project component options: ### Build the Arrow Acero Engine Module set(ARROW_ACERO "ON") ### Build Arrow commandline utilities set(ARROW_BUILD_UTILITIES "OFF") ### Build all Arrow Compute kernels set(ARROW_COMPUTE "ON") ### Build the Arrow CSV Parser Module set(ARROW_CSV "ON") ### Build the Arrow CUDA extensions (requires CUDA toolkit) set(ARROW_CUDA "OFF") ### Build the Arrow Dataset Modules set(ARROW_DATASET "ON") ### Build the Arrow Filesystem Layer set(ARROW_FILESYSTEM "ON") ### Build the Arrow Flight RPC System (requires GRPC, Protocol Buffers) set(ARROW_FLIGHT "ON") ... ``` [ArrowOptions.cmake.txt](https://github.com/apache/arrow/files/13045993/ArrowOptions.cmake.txt) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
