Thanks for these suggestions. Will take a look into these approaches.
With Regards,
Vibhatha Abeykoon
On Fri, Nov 6, 2020 at 2:43 PM Uwe L. Korn wrote:
> The pip package (explicitly the wheels) should contain the C++ libraries
> and headers. So it should be sufficient for your usecase and
The pip package (explicitly the wheels) should contain the C++ libraries and
headers. So it should be sufficient for your usecase and there shouldn't be a
need for separately building the C++ artifacts.
On Fri, Nov 6, 2020, at 5:18 PM, Vibhatha Abeykoon wrote:
> One more question about
Another approach I took is;
https://github.com/vaexio/vaex-arrow-ext
But it uses pybind11, not cython.
(from mobile phone)
On Fri, 6 Nov 2020, 17:19 Vibhatha Abeykoon, wrote:
> One more question about packaging, here when the API requires both Cython
> and C++ APIs,
> Pyarrow dependency must
One more question about packaging, here when the API requires both Cython
and C++ APIs,
Pyarrow dependency must also be built from the source? Or is it practical
to use the same version
of Arrow using Pip?
With Regards,
Vibhatha Abeykoon
On Fri, Nov 6, 2020 at 9:59 AM Vibhatha Abeykoon wrote:
Hello Uwe,
Nice example. I will follow this.
With Regards,
Vibhatha Abeykoon
On Fri, Nov 6, 2020 at 9:36 AM Uwe L. Korn wrote:
> Hello Vibhatha,
>
> the best is to set a relative RPATH on the libraries. An example for this
> can be seen in the turbodbc sources:
>
Hello Vibhatha,
the best is to set a relative RPATH on the libraries. An example for this can
be seen in the turbodbc sources:
https://github.com/blue-yonder/turbodbc/blob/80a29a7edfbdabf12410af01c0c0ae74bfc3aab4/setup.py#L186-L189
Cheers
Uwe
On Tue, Nov 3, 2020, at 11:44 PM, Vibhatha
Hello,
I have a question related to packaging an API written by using both C++ API
and Cython API of Arrow.
For now what I do is, build Arrow from source to generate both libarrow.so
and libarrow_python.so. When using the library, I have to point the
installed *.so using the LD_LIBRARY_PATH. But
