Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: Erik.Hardy@sei.cmu.EDU
Newsgroups: comp.windows.x
Subject: Problems with X11 (tree) in non-standard location
Message-ID: <9103221557.AA11186@ir.sei.cmu.edu>
Date: 22 Mar 91 15:57:25 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 26


[Martin Brunecky is still having problems getting the right location for
include files in using Imake. He tried:]

649c649,650
<         IMAKE_CMD = $(IMAKE) -DUseInstalled -I$(IRULESRC) $(IMAKE_DEFINES)
---
>         IMAKE_CMD = $(IMAKE) -DUseInstalled -DDestDir=$(DESTDIR) \
>                         -I$(IRULESRC) $(IMAKE_DEFINES)

This'll work just fine. Another way is to set the environment variable
IMAKEINCLUDE, e.g.

	setenv IMAKEINCLUDE "-I<yourdir>"

This has the effect of adding "-I<yourdir>" to the command line. "." is
always first on the list, followed by your directory. You can specify
multiple directories, separated by spaces, but you need -I for each one.

This also lets you put anything else on the command line implicitly, so that,
for instance, you can define things using the -D option. Although this is
non-standard usage, it can be really handy in cutting down on the amount
of stuff you have to type.

erik hardy
sei/user interface project