2000.04.19 13:53 "Re: autoconf based configure", by Chris Hanson
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.
Obviously you aren't a Macintosh developer then.
The Macintosh does not have any sort of underlying command-line environment. Period. You can get Macintosh Programmer's Workshop, which is an application that implements a command-line development environment (a rather nice one, in fact) but it is only Unix-like and most definitely not Unix-compatible.
I am opposed in the strongest possible terms to messing libtiff up with autoconf unless specific allowances are made for platforms for which autoconf is not an option.
Basically, if autoconf is just used to: (1) set up a few constants in a configuration header **and there is documentation of what these are, what they do, and why they're needed**, (2) handle things like making libtiff a shared library on different Unix variants, and (3) handle locating required libraries & headers and supplying the appropriate include paths to the compiler on different Unix variants, I could handle that because I could just generate the Macintosh version of that header and the necessary CodeWarrior projects or MPW makefiles by hand.