AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2000.04.17 09:38 "GNU autoconf macro for libtiff checking", by Jan Prikryl
2000.04.18 18:00 "Re: SGI tiff 3.5.5 make install error .....", by Sam Leffler
2000.04.18 09:38 "Re: SGI tiff 3.5.5 make install error .....", by M. L. Welles
2000.04.17 19:03 "SGI tiff 3.5.5 make install error .....", by Hezekiah Mcmurray
2000.04.18 06:19 "Re: SGI tiff 3.5.5 make install error .....", by Jan Prikryl
2000.04.18 14:42 "Re: SGI tiff 3.5.5 make install error .....", by Jan Prikryl
2000.04.18 19:29 "Re: SGI tiff 3.5.5 make install error .....", by Frank Warmerdam
2000.04.19 02:19 "autoconf based configure", by Kiriakos Georgiou
2000.04.19 13:53 "Re: autoconf based configure", by Chris Hanson
2000.04.18 18:36 "Re: SGI tiff 3.5.5 make install error .....", by Chris Hanson
2000.04.18 18:51 "Re: SGI tiff 3.5.5 make install error .....", by Sam Leffler
2000.04.19 16:48 "Re: SGI tiff 3.5.5 make install error .....", by Roy Darrall
2000.04.19 18:39 "Re: SGI tiff 3.5.5 make install error .....", by Bob Friesenhahn
2000.04.20 14:02 "Re: SGI tiff 3.5.5 make install error .....", by Bruce Cameron

2000.04.19 02:19 "autoconf based configure", by Kiriakos Georgiou

My main concern is that a shift to a new configuration mechanism will cause hassles for a while. Files that get forgotten, DSO support that might be lost of some platforms. However, it might make it practical to make libtiff configuration "smarter" about stuff like using libjpeg, libz and other stuff if available on the system.

I've been using autoconf for a few years and I like it. I believe we have people with every machine imaginable so it will be quickly tuned to handle everything simply with a ./configure && make && make install just like all good free s/w.

-K