httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sascha Schumann <sas...@schumann.cx>
Subject Re: How to build 2.0 with autoconf
Date Wed, 26 Jan 2000 17:51:16 GMT
On Fri, Jan 21, 2000 at 06:35:31PM +0100, Ralf S. Engelschall wrote:
> 
> In article <200001211541.IAA28926@sanitas> you wrote:
> > In a recent note, Ralf S. Engelschall said:
> > 
> >> Date: Fri, 21 Jan 2000 16:17:52 +0100
> >> 
> >> Once ago for those who now want to listen: For Apache (where non-Unix
> >> and some non-standard Autoconf features like shadow trees, etc. have
> >> to be supported), Autoconf can be a great benefit, but should be used
> > 
> > In the GNU tradition, shadow trees are well supported by "configure".
> > _However_ the GNU model is different from APACI; rather than building
> > a tree of symlinks to all the sources, it puts only products in the
> > shadow trees, and relies on VPATH to access the sources.  VPATH is
> > provided by GNU make, and several other vendors' make, but is not
> > universal; not even POSIX, AFAIK.
> 
> Yes, I know that the GNU way is VPATH. But exactly because it's not
> universal and would have required changes to the existing Makefiles
> APACI's variant was born. And I think even for Apache 2.0
> the situation will be not much different ;)

    I think we can provide both. VPATH is supported by most
    Unices' makes (Solaris, *BSD, Linux); and if it is not
    supported on a particular platform, one can fall back to
    mkshadow.

> Is it now more clear what point I want to address?

    Sounds like a big

    case "$OS" in
    foo)
        specific stuff;;
    bar)
        more specific stuff;
    *) 
        $srcdir/configure $@;;
    esac

-- 

          Regards,

                            Sascha Schumann
                                 Consultant

Mime
View raw message