-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28/03/12 11:12, Jan Just Keijser wrote: > Hi, > > Gert Doering wrote: >> Hi, >> >> On Mon, Mar 26, 2012 at 07:51:01PM +0200, Alon Bar-Lev wrote: >> >>> The benefit is to divide the code into libraries and core which >>> is easier to maintain and reuse. >>> >> >> I'm not sure I understand what's so hard about "compile stuff, use >> 'ar' to pack into libopenvpn.a" that stuff needs more convolutions. >> >> We're not building a shared library - which I agree is major pains >> unless handled by libtool. But static libraries are easy on about >> everything (except Windows, can't speak about that). >> >> > actually, most of the problems I've seen with libtool have to deal > with shared libraries - I would NOT trust libtool to be able to build > shared libraries the way I want it to, esp when shared libs use other > shared libs. don't know if libtool 2.x solves the issues found in 1.5 > >>> Anyway, new automake does support silent rules, try the >>> following[1] patch and see if it makes you happier. >>> >> >> This is missing the point: I think what automake/autoconf is doing >> now is much too complicated. I *like* to see what it's doing, and >> hiding complexity by just not showing it is a step into the wrong >> direction. >> >> > I fully agree with Gert here; if we can avoid libtool then I'd really > like to do so - it only adds an extra layer that (IMHO) is not needed; > what was wrong with the "old" method?
I'm not sure if this changes your point of view, but we're not building a shared library like an '.so' file which is dynamically loaded upon execution of OpenVPN. What's happening is that a static library is built and the linker pulls in the needed pieces from the libcompat.a file at build time. In that regards, the compat/ directory is a separate entity which will be easier to maintain. If we in the future f.ex. are missing some POSIX functions on some platforms, we just add a port of those functions here - and rebuild OpenVPN. No other changes to OpenVPN would normally be needed. And as it's all statically linked, there's no extra files or packaging dependencies to think of. kind regards, David Sommerseth -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9y2UkACgkQDC186MBRfrqwPgCbBvb8tTTOZ7c2l+fDv1e3oVdl rMEAn0sMU9u7R3LLLTN18BpmQWl+fh5o =US/Q -----END PGP SIGNATURE-----
