raulcd commented on PR #45580: URL: https://github.com/apache/arrow/pull/45580#issuecomment-2681482048
I think the current plan, or at least the latest conversations, were to move our build-backend to [scikit-build-core](https://github.com/scikit-build/scikit-build-core). Adding more custom options to our `setup.py` seems that will make that migration even more complex. I understand the appeal but this will still fail for people building from source from pypi for example and only helps downstream package maintainers that want to build pyarrow from source cloning the repo, right? which at that point requires a couple commands to build Arrow C++: ```bash cmake -S arrow/cpp -B arrow/cpp/build \ -DCMAKE_INSTALL_PREFIX=$ARROW_HOME \ --preset ninja-release-python cmake --build arrow/cpp/build --target install ``` @tiran when you say your downstream builds are much easier to maintain, could you share a link on how are you currently building Arrow C++? Is that you would like to get rid of the manual cmake commands? -- 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]
