Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!BRL.MIL!phil
From: phil@BRL.MIL (Phil Dykstra)
Newsgroups: comp.windows.x
Subject: Re:  Stupid Imake question
Message-ID: <8902282128.aa17018@SPARK.BRL.MIL>
Date: 1 Mar 89 02:28:51 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 37

Confusion over the use of imake is common enough that this is worth
spelling out:

1) Get a copy of ximake.sh in the MIT core distribution under
   util/scripts/ximake.sh.

2) Install it as /usr/bin/X11/ximake (or wherever your binaries are)
   and make it executable.

3) To configure X software with an Imakefile simply say:

	ximake $XTOPDIR

   where $XTOPDIR is the location of the top of your X11 source
   tree (e.g. /usr/src/X11).  This will generate a Makefile from
   the Imakefile.  You can then run "make depend", "make", "make
   install", etc., just as with a normal Makefile.

I went one step farther and edited the ximake script to default to
the source tree location on my machine.  Then you only have to say
"ximake" to generate the Makefile.

One limitation of the above is that you do need to have access to
the source tree on the machine you run imake from (since it gets
the imake macro files out of util/imake.includes and links to the
libraries and header files in the source tree).  The MIT folks have
said that R4 should remove this restriction.

For those of you that still avoid Imakefiles, I point out that you
almost ALWAYS have to edit a Makefile to successfully install new
software, but almost NEVER have to edit Imakefiles.

Try it, you'll like it.

- Phil
<phil@brl.mil>
uunet!brl!phil