[JDEV] Shared Libraries
scott at tranzoa.com
Thu Aug 19 02:12:40 CDT 1999
Personally, and note this is a personal opinion, I would compile libpth into
libjabber statically by default and have libjabber be a shared library. Why?
libpth isn't usually on systems by default and libjabber (at least in my
environment) will want to be transported directly between machines. As for
libjabber itself, having it shared makes it easier for multiple jabber
clients on a single machine. JNIX and Kruft on the same client? I think
Of course, leave the option for switching between shared and static. I'll
be the first packaging a RPM for it depending on pth. :)
* Jeremie translated into ASCII [Thu, Aug 19, 1999 at 01:42:33AM -0500][<Pine.LNX.4.10.9908190134240.8353-100000 at lor.jeremie.com>]
> I don't have a ton of experience in this area, so I'm going to throw it
> out here and try to get some feedback...
> Background: we're currently working on a common library for jabber that
> contains most of the core XML and protocol functionality. This library is
> threaded via pth, yet another library.
> What I'm wondering is, first, should libpth be compiled statically into
> libjabber (since it's required anyway)? Second, should libjabber be
> compiled statically into applications by default? If not, what's the best
> way to handle it?
> I know the tools we're using, autoconf, automake, and libtool, can handle
> just about any configuration, I'm just not sure which way things should be
> by default or what is the "correct" way to do it.
> jdev mailing list
> jdev at jabber.org
More information about the JDev