WillAyd commented on issue #36411: URL: https://github.com/apache/arrow/issues/36411#issuecomment-3916925502
> [@WillAyd](https://github.com/WillAyd) Do you have a specific use case in mind for this? I think the most compelling case is to make it easier for developers, but there are issues that have been opened requesting this feature like https://github.com/apache/arrow/issues/45576 Meson makes that much simpler than CMake I think because of the way it handles subprojects, alongside it offering the wrap system. > I think the main difficulty for a PyArrow sanitizers build is that the sanitizer instrumentation should be enabled in CPython as well (and potentially NumPy?). That's an ideal setup but I don't think its required - you could use point LD_PRELOAD to the sanitizer library to have it loaded correctly from a process that was not built with sanitizers enabled (i.e. Python). We used to do that in CI with pandas, although we did abandon it after time due to it being a maintenance burden > I think it is perfectly reasonable to pursue scikit-build-core as the option that will provide the most improvement for the time Raul has to spend on this right now, and is also completely reasonable given that Arrow C++ maintainers have a lot of experience debugging CMake and will continue to invest in that build system for the foreseeable future. I don't think that rules out Meson Python if there is an interested contributor. I think that's reasonable. CMake is definitely the path of least resistance right now, and regardless of which build system is better from a bigger picture perspective, I think would still represent an incremental upgrade over setuptools -- 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]
