httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <>
Subject Re: Makefile suggestions?
Date Fri, 08 Oct 1999 15:55:39 GMT
I'll try to explain what I'm aiming at and see if it makes sense to you, the
viewing public!

The VPATH isn't that important as there are other ways round it, but I
always like neat and tidy solutions, not messy horrible ones.

What I'd like is that when we have a new platform being added to APR they
look at the unix code then go from there.

e.g. The new platform can use almost all of the network code but need a
different poll (for some weird reason).  They simply have to create a
directory alongside unix, create their poll.c file, add a (that
can be copied from A.N.Other directory) and alter to reflect
the fact that they have their directory.

This is neat, clean and incredibly quick/easy to do.  It keeps the
directories clean and allows people to easily track what will need looked at
when getting code up to date.  I appreciate what Brian and the others are
saying and I don't want to make life difficult.  If a platform HAS to have
the dependencies then it can have Brian's solution, if it doesn't need them
then it could use VPATH.  I think both are viable options that solve the

----- Original Message -----
From: Brian Havard <>
To: <>
Sent: 08 October 1999 14:48
Subject: Re: Makefile suggestions?

> On Fri, 8 Oct 1999 10:46:54 +0100, David Reid wrote:
> >The VPATH works like a dream and makes it very easy to do what I had in
> >mind.  Thanks for the hint!
> I just tried this technique (for the OS/2 time directory) and it works
> for me apart from one hitch, "make depend" doesn't work and I can see any
> easy work-around.
> On the other hand, using my suggestion of having a source file that just
> #includes the unix source works just fine with make depend and doesn't
> on any special make voodoo.
> --
>  |  Brian Havard                 |  "He is not the messiah!
>  |  |  He's a very naughty boy!" - Life of
Brian |
>  -------------------------------------------------------------------------

View raw message