eli-schwartz commented on issue #36411: URL: https://github.com/apache/arrow/issues/36411#issuecomment-3908774534
> I personally find meson nicer to work with than CMake but it is fair to say that Arrow C++ will possibly stay with CMake for the moment and the current flag integration is much simpler than what we have with the current `meson-python` solution. I am unsure what will be the experience for python-devs of PyArrow or users trying to build PyArrow with the current integration with Arrow C++. > Given that Arrow C++ will probably stay on CMake, I think reusing the existing CMake infrastructure via `scikit-build-core` is the more pragmatic path forward. If I'm understanding correctly, you are suggesting it may make sense to take advantage of code duplication specifically? I would personally not make that decision myself -- if you also find something else "nicer to work with" then doing a bit of repetitive work should be a reasonable price to pay for having a nicer experience. Of course if others find CMake nicer to work with than Meson, that would be a useful data point for pleasant developer experiences, which would then argue in favor of using that. -- 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]
