Hi Andreas, > Is there any way to have different library sections in setup.py > to accomplish version specific libraries linked?
- libraries = ['freecontact', 'boost_python'])] + libraries = ['freecontact', 'boost_python-py36'])] This hack fixes the python 3.6 .so linkage. I'm not sure whether there is a better way to workaround this, but the following solution works fine - libraries = ['freecontact', 'boost_python'])] + libraries = ['freecontact', 'boost_python-py%d%d'%(sys.version_info[0], sys.version_info[1])])] works for all python versions, i.e. 2.7, 3.6, 3.7 . BTW, Please check you boost-python version: │ │ /t/x/python-freecontact ❯❯❯ dpkg -L libboost-python1.62.0 │ /. │ /usr │ /usr/lib │ /usr/lib/x86_64-linux-gnu │ /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.62.0 │ /usr/lib/x86_64-linux-gnu/libboost_python-py36.so.1.62.0 │ /usr/lib/x86_64-linux-gnu/libboost_python-py37.so.1.62.0 │ /usr/share │ /usr/share/doc │ /usr/share/doc/libboost-python1.62.0 │ /usr/share/doc/libboost-python1.62.0/changelog.Debian.gz │ /usr/share/doc/libboost-python1.62.0/copyright │ /usr/share/lintian │ /usr/share/lintian/overrides │ /usr/share/lintian/overrides/libboost-python1.62.0 │ /t/x/python-freecontact ❯❯❯ apt list libboost-python1.62.0 │ Listing... Done │ libboost-python1.62.0/unstable,unstable,now 1.62.0+dfsg-6 amd64 [installed,automatic] │
