Geoff Hutchison writes:
>
> The problem is that from a user perspective, the two flags are
> inconsistent. What does it mean to use --with-zlib --disable-zlib? Whic
> has precence? If we want to use --with-zlib, then we should remove
> --disable-zlib and make a note in the documentation.
>
> I used --disable because I intended that zlib be compiled in by default
> and the config option would allow users to pick whether it was used (or
> the compression level).
>
The advantage of --with is that it allows the user to specify the
installation directory of zlib if not the standard /usr or /usr/local.
I've upgraded all that:
. Removed the --disable-zlib
. Encapsulate the zlib detection in AM_WITH_ZLIB (in acinclude.m4)
. Explicit comment when configure --help is called:
--with-zlib=DIR root directory path of zlib installation [defaults to
/usr/local or /usr if not found in /usr/local]
--without-zlib to disable zlib usage completely
Berkeley DB now also uses AM_WITH_ZLIB. Having acinclude.m4 will hopefully
remind us that it's better to write a simple macro than writing hairy
tests in configure.in.
I hope this satisfies everyone. Let me know if you want something else.
Cheers,
--
Loic Dachary
ECILA
100 av. du Gal Leclerc
93500 Pantin - France
Tel: 33 1 56 96 09 80, Fax: 33 1 56 96 09 61
e-mail: [EMAIL PROTECTED] URL: http://www.senga.org/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
