Also no concrete answer, but one such example is turbodbc, I think. But it seems they only have conda binary packages, and don't distribute wheels .. (https://turbodbc.readthedocs.io/en/latest/pages/getting_started.html), so not that relevant as comparison (they also need to build against an odbc driver in addition to arrow). But maybe Uwe has some more experience in this regard (and with attempts building wheels for turbodbc, eg https://github.com/blue-yonder/turbodbc/pull/108).
Joris On Thu, 2 Jul 2020 at 11:05, Antoine Pitrou <anto...@python.org> wrote: > > > Hi Maarten, > > Le 02/07/2020 à 10:53, Maarten Breddels a écrit : > > > > Also, I see pyarrow distributes manylinux1/2010/2014 wheels. Would a vaex > > extension distributed as a 2010 wheel, and build with the pyarrow 2010 > > wheel, work in an environment where someone installed a pyarrow 2014 > > wheel, or build from source, or installed from conda-forge? > > I have no idea about the concrete answer, but it probably depends > whether the libstdc++ ABI changed between those two versions. I'm > afraid you'll have to experiment yourself. > > (if you want to eschew C++ ABI issues, you may use the C Data Interface: > https://arrow.apache.org/docs/format/CDataInterface.html > though of course you won't have access to all the useful helpers in the > Arrow C++ library) > > Regards > > Antoine. > >