Hi! On 2015-03-18 at 18:06 (CET), Daniel P. Berrange wrote: > Entangle has always built its code as a library, but previously it > statically linked this into the final binary. I found that this was > causing problems for plugins though, because the linker will drop > any functions which are not used by the main program. It was dropping > a bunch of code from the static library, which was none the less > wanted by the plugins. Switching to a shared library ensured that > the code was always available to plugins, at the cost that the libs > become visible. > > These libraries cannot be used in isolation at this time though. For > a start we don't include the header files, nor do I intend to promise > any kind of API stability. So IMHO, splitting them into a -libs > package is a waste of time, and gives a misleading impression to > users that the libraries are useful on their own. It is purely an > internal detail of the app right now. > > Also note it is possible these libraries will go away again in the > future if I figure out a better way to avoid the linker problems.
Perfect. Thanks a lot for clarifying your vision of the libs usage. I'll then keep those two libs in the main binary package, overriding the warning. 0.7.0 will be shortly in Debian experimental suite. ;-) Cheers. -- Matteo F. Vescovi _______________________________________________ Entangle-devel mailing list Entangle-devel@gna.org https://mail.gna.org/listinfo/entangle-devel
