Status: Read
Received: from [207.176.88.85] by phillip.cerious.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Wed, 19 Apr 2000 10:27:21 -0400
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id JAA29599;
	Wed, 19 Apr 2000 09:56:15 -0400
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Wed, 19 Apr 2000 09:53:22 -0400
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id JAA29486
	for tiff-outgoing; Wed, 19 Apr 2000 09:53:22 -0400
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from mail.totalint.com (209-9-140-130.sdsl.cais.net [209.9.140.130])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id JAA29481
	for <tiff@olympiakos.com>; Wed, 19 Apr 2000 09:53:18 -0400
Received: from [209.9.140.163] by mail.totalint.com (post.office MTA v
          ID# 0-8000) with ESMTP id APH for <tiff@olympiakos.com>;
          Wed, 19 Apr 2000 08:53:18 -0500
X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410)
Date: Wed, 19 Apr 2000 08:53:16 -0500
Subject: Re: autoconf based configure
From: chanson@totalint.com (Chris Hanson)
To: tiff@olympiakos.com
Mime-version: 1.0
X-Priority: 3
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Message-ID: <AIG.APH>
Sender: owner-tiff@olympiakos.com

Kiriakos Georgiou <kg@gate7.olympiakos.com> wrote:
> 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.

  -- Chris
