Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!bin
From: bin@primate.wisc.edu (Brain in Neutral)
Newsgroups: comp.windows.x
Subject: Re: Alternative installation directories for X11R4
Message-ID: <3984@uakari.primate.wisc.edu>
Date: 28 Feb 91 19:02:24 GMT
References: <1991Feb28.060558.21908@en.ecn.purdue.edu>
Sender: bin@primate.wisc.edu
Reply-To: bin@primate.wisc.edu
Lines: 31

From article <1991Feb28.060558.21908@en.ecn.purdue.edu>, by milton@en.ecn.purdue.edu (Milton D Miller):
|>Wouldn't it work to put
|>
|>INCLUDES = -I/tmp/cpp/whatever
|>
|>in your Imakefile?  
| [...]
|>but INCLUDES is the one intended
|>for you to be able to use yourself.
| 
| INCLUDES Is for the APPLICATION SPECIFIC includes.  Why would you want
| to edit every Imakefile, when it is taken care of by TOP_INCLUDES ?  I
| don't think this was one of the changes I made while installing R4 with
| DESTDIR=/tmp/four (don't ask).  I didn't have to make many (any?)
| changes for the programs I wanted, but I didn't remake programs that
| were already in R3.  I did make some net stuff, though.  (TOP_INCLUDES
| and INCLUDES are combined with STD_INCLUDES and some others).  (Getting
| the config figured out is another matter).

Well, that's OK, but it sounds to me like you're talking about building
part of the X distribution, whereas the poster to which I was replying
was, despite the article title, building his own applications, and wanting
to *access* includes installed in a non-standard place (not install them
there).  So he could just as well use the application specific include
symbol.

Your solution would work, too, I think.

--
Paul DuBois
dubois@primate.wisc.edu