Date: Tue, 2 Sep 1997 17:18:34 -0700 (PDT)
From: Dean Gaudet <dgaudet@arctic.org>
To: new-httpd@apache.org
Subject: Re: Timeframe for 1.3?
In-Reply-To: <ML-2.3.873229771.5089.rasmus@inet-dev>
Message-ID: <Pine.LNX.3.95dg3.970902171754.27935O-100000@twinlark.arctic.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Oh yeah, related to this ... multidirectory projects I've worked on
frequently have an include directory where all the .hs live ... so that
only a single -I is necessary rather than having to -I all the different
directories.

Dean

On Tue, 2 Sep 1997 rasmus@bellglobal.com wrote:

> > More seriously, if you are planning on PHP 3.0 being out in the next few
> > months you would be well advised to have 1.2 support, even if it isn't
> > pretty.  Or you could include a patch to make the 1.2 Configure do the 1.3
> > stuff with it.
> 
> Perhaps we could sneak the 1.3-style Configure code into 1.2.5 if for some
> reason a 1.2.5 becomes necessary?
> 
> The other problem I have is that the httpd.h file is in different places
> between the two versions.  In order to figure out which version I am dealing
> with I need to check the MODULE_MAGIC_NUMBER in httpd.h.
> 
> Right now for PHP 3.0 I have to tell the user to go to his Apache directory
> and look around for httpd.h somewhere under there.  And once found, to 
> start the PHP configure script with something like:
> 
>   ./configure --with-apache=/usr/local/src/apachen/src/main
> 
> I suppose I could write something which did the hunting for them and just
> have them enter the top-level Apache dir.
> 
> -Rasmus
>