On Wed, Mar 20, 2002 at 06:09:33PM -0500, Charles Wilson wrote: >(In the old days, making a DLL required intrusive and exhausting changes >to lots and lots of source files -- __declspec(dllexport) this, >__declspec(dllexport that)... -- but no longer.) With auto-import >binutils, and the libtool-devel package, you merely: > >rm ldconfig.sh >rm ltmain.sh > << edit configure.in and make sure that > it AC_PREREQ's 2.50 or greater >> >libtoolize --force -c >aclocal ( possibly need to add '-I some-subdir') >automake --force -a >autoconf > >And then configure/make as usual -- an poof! DLL AND static lib.
I don't think that tcp wrappers uses configure or libtool, though. Or it didn't the last time I looked at it. >Okay, maybe it's not QUITE that easy, but it's close. You do need to >understand the autotools and maybe read a few man pages, but... > >Still, this is a maintainer decision. If you don't want to DLLize, that >is your prerogative. No complaints from me. Nor from me. It was just a suggestion. I don't think I've ever seen a shared version of libwrap, actually. cgf
