Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Sender: trawick@bellsouth.net
To: new-httpd@apache.org
Subject: Re: architecture-specific directories
References: <Pine.LNX.4.21.0011141219190.20154-100000@koj.rkbloom.net>
From: Jeff Trawick <trawickj@bellsouth.net>
Date: 14 Nov 2000 15:28:57 -0500
In-Reply-To: rbb@covalent.net's message of "Tue,
 14 Nov 2000 12:20:48 -0800 (PST)"
Message-ID: <m3u29ab8mu.fsf@adsl-77-241-65.rdu.bellsouth.net>
Lines: 28
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

rbb@covalent.net writes:

> > Let's stop and remember that *users* do not need dependencies. If they
> > unpack the distribution, they are simply going to compile everything.
> > Dependencies in the makefiles will not help them whatsoever.
> > 
> > Given that dependencies are only for *us*, then let's solve the problem for
> > us. Specifically, this means that when *we* generate the dependencies, we'll
> > be doing it on the appropriate platform. And if we assume the dependencies
> > won't get checked in, then everything should be fine.
> > 
> > That gives us proper dependencies and keeps the platform stuff out of the .c
> > files.
> > 
> > [ I think this simply means that we generate the depencencies into
> >   "Makefile" rather than "Makefile.in" ]
> 
> Small problem with that.  As Jeff said, he can't generate dependancies on
> OS/390, and I'm not sure David can on BeOS.  

My thought on this is that the build-the-dependencies script can be
updated over time to support non-gcc mechanisms for building the
dependencies. 

-- 
Jeff Trawick | trawick@ibm.net | PGP public key at web site:
     http://www.geocities.com/SiliconValley/Park/9289/
          Born in Roswell... married an alien...