[C++-sig] distributing libraries built using Boost.Python

[Stefan Seefeld]

Hi Danielle,


On 2018-10-16 11:41 AM, danielle amethyst brake wrote:
> Hi Boost.Python friends,
>
> I have a library, which consists foremostly of a set of bindings built 
> using Boost.Python, and I am finding distribution to be a barrier.  
> Requiring the user to build themselves prevents most of my users from, 
> well, being users. Hence, I am writing today to query about 
> best-practices and ideas on how to distribute my Python library, that 
> consists of pure Python code installable via pip, a built .so library, 
> and an underlying .so/.a/.dyld/whatever core library also built from C++.

the biggest issue really is ABI compatibility, i.e. you can't simply 
distribute a C++ library such as Boost.Python compiled with one 
compiler, and expect it to work in machines with arbitrary other 
compilers (or compiler versions). Once the set of supported compilers / 
compiler versions is settled, it's much easier to share binaries.

If you are mainly working with Python, i.e. if your C++ code is only 
used in extension modules, you may consider using Anaconda, which 
provides some structure in its package management that could help you 
and your users.

Cordially,

Stefan

--

       ...ich hab' noch einen Koffer in Berlin...
     

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cplusplus-sig/attachments/20181019/df1c4093/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.png
Type: image/png
Size: 1478 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/cplusplus-sig/attachments/20181019/df1c4093/attachment.png>