Re: private library whci is not that private

2019-07-17 Thread Andrey Rahmatullin
On Wed, Jul 17, 2019 at 01:18:55PM +, PICCA Frederic-Emmanuel wrote: > > Are python modules public or only designed to be used by the app? > > It seems that this module must be public. Must? In that case I find it strange that the librray API is published as a Python binding but not as

Re: private library whci is not that private

2019-07-17 Thread Andrey Rahmatullin
On Wed, Jul 17, 2019 at 08:40:36AM +, PICCA Frederic-Emmanuel wrote: > I am preparing a package knows as bornagain. > > 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. Are python modules

Re: private library whci is not that private

2019-07-17 Thread merkys
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 >

private library whci is not that private

2019-07-17 Thread PICCA Frederic-Emmanuel
Hello, I am preparing a package knows as bornagain. 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 under