On Thursday 11 March 2004 4:22 pm, Tom Collins wrote: > On Mar 11, 2004, at 3:06 PM, Nick Harring wrote: > > I've uploaded a patch to the sourceforge project which applies to > > 5.4.(2|3) and 5.5.0 which adds a configure option > > --enable-shared-library and its corollary --disable-shared-library. The > > default is for this to be on, and it causes a libvpopmail.so to be > > built > > and linked against for the vpopmail binaries. For the vpopmail binaries > > this isn't such a big deal, but for anything linking against vpopmail > > which doesn't force static linking this can save a lot of work down the > > road. > > I saw in Tom's plans for 5.5.x that he wants this included down the > > road. I've done some testing with no glitches so far and am planning on > > putting it in my production environment (about 80K accounts) in the > > future, so I have some confidence in this, but in the end this is still > > beta at best. Its all makefile modifications, so it should be quite > > safe. > > > > The only caveat is that right now you must run autoconf then aclocal > > then automake. > > Please let me know if people have issues with it, however I'm not the > > worlds greatest autoconf/automake person, so its very possible I won't > > be able to help. > > I have done some work with Nick's original patch, and plan to roll it > into 5.5.1. I wanted to release 5.5.0 without the patch, and have the > 5.5.1 release focused solely on the shared library patch. This should > make it easy to back out of certain features further down the road. > > I'm not sure that there's a need to disable the shared library option > -- I'd like to always build it.
I'd like to be able to disable shared libraries. I like not having run time linking each time vchkpw and vdelivermail are run. I'd rather link once at compile time. Makes it just-a-bit-more efficent. The only thing it would save me is recompiling vpopmail dependent libraries on an update, and that's not a big deal for me. Ken Jones
