jorisvandenbossche commented on code in PR #14333: URL: https://github.com/apache/arrow/pull/14333#discussion_r992258072
########## docs/source/python/integration/extending.rst: ########## @@ -50,12 +50,23 @@ This will not include other parts of the Arrow API, which you will need to include yourself (for example ``arrow/api.h``). When building C extensions that use the Arrow C++ libraries, you must add -appropriate linker flags. We have provided functions ``pyarrow.get_libraries`` -and ``pyarrow.get_library_dirs`` which return a list of library names and +appropriate linker flags. We have provided functions ``pa.get_libraries`` +and ``pa.get_library_dirs`` which return a list of library names and likely library install locations (if you installed pyarrow with pip or conda). These must be included when declaring your C extensions with setuptools (see below). +.. note:: + + The PyArrow-specific C++ code is now a part of the PyArrow source tree + and not Arrow C++. That means the header files and arrow_python library + are not necessarily installed in the same location as that of Arrow. Review Comment: Yes, and for this specific use case (and if you are already building against arrow anyway), using the C Data Interface is also more complex than using of the wrap/unwrap functions. @AlenkaF I would still add something along the lines of ".. and will no longer be automatically findable by CMake" (my original comment in this thread) -- 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]
