Re: private library whci is not that private
Hi Frederic-Emmanuel,
On 2019-07-17 11:40, PICCA Frederic-Emmanuel wrote:
> this software provide a GUI application and a python modules generated via swig.
> part of the code is shared between the binary and the modules.
>
> the upstream put the library
>
> _libBornAgainCore.so
> _libBorAgainFit.so
> _libbornagainGUI.so
(First of all, is there a typo in "_libBorAgainFit.so"?)
From my experience, SWIG-generated shared libraries for Python usually
belong next to the importing files. For example [1]:
/usr/lib/python3/dist-packages/pycodcif/__init__.py
/usr/lib/python3/dist-packages/pycodcif/_pycodcif.cpython-37m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/pycodcif/pycodcif.py
I expect that in the case of bornagain, libBornAgainFit.py looks for
_libBornAgainFit.so in the same directory,
/usr/lib/python3/dist-packages/bornagain/.
Hope this helps,
Andrius
[1] https://packages.debian.org/sid/amd64/python3-pycodcif/filelist
Reply to: