Date: Wed, 13 Nov 1996 14:45:26 -0400 (EDT)
From: Doug MacEachern <dougm@osf.org>
Reply-To: Doug MacEachern <dougm@osf.org>
Subject: Re: location of httpd.h (Was: logging before exit) (fwd) 
To: new-httpd@hyperreal.com
Cc: The Perl/Apache Mailing List <modperl@listproc.itribe.net>
In-Reply-To: <9611121611.aa09923@paris.ics.uci.edu>
Message-Id: <Pine.3.07.9611131424.A29831-b100000@defiant.osf.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

On Tue, 12 Nov 1996, Roy T. Fielding wrote:

> >>> I'd suggest both parties follow the tradition. Apache should have a
> >>> 'make install' that installs both binary and header file, and modperl
> >>> should not insist on seeing the apache source but should ask for the
> >>> installed header file. (And search for it in /usr/local/include etc.)
> 
> No way -- httpd.h is an internal configuration file which is specific
> to a particular server source tree (remember, there may be more than one
> on a machine).  It doesn't belong outside the apache tree.  

True, good point.

> Why don't
> they just setup a modules/mod_perl/* directory and then refer to it
> as ../../httpd.h (or, better, just as httpd.h and let make set up
> the -I options).

This is exactly what mod_perl does now.  But, there are two sides of the build, the
apache part (httpd + libmodperl.a) and the perl part, several modules built and
installed by Perl's MakeMaker, one of which is Apache::Constants who needs httpd.h.
Rob wants to build the httpd binary once, then install the perl side on other machines
without taking the apache source tree along too.
We'll come up with another solution...

-Doug

> 
> .....Roy