Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!sdd.hp.com!ucsd!ucbvax!bloom-beacon!eru!luth!sunic!mcsun!ukc!harrier.ukc.ac.uk!rlh2
From: rlh2@ukc.ac.uk (Richard Hesketh)
Newsgroups: comp.windows.x
Subject: Re: R5 Wish List (Imake to the bitbucket)
Message-ID: <5130@harrier.ukc.ac.uk>
Date: 18 Jul 90 11:11:16 GMT
References: <2767@uakari.primate.wisc.edu> <675@venice.SEDD.TRW.COM>
Reply-To: rlh2@ukc.ac.uk (Richard Hesketh)
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 24
Summary:
Expires:
Sender:
Followup-To:

In article <675@venice.SEDD.TRW.COM> baur@venice.SEDD.TRW.COM (Steven L. Baur) writes:
>I have had *wonderful* results with Imake on a SUN3/OS4.03->4.1 with all-MIT
>sources, and don't see any particular need to make it go away.  I wish though
>that there wasn't so much (apparent to me, a novice X administrator)
>dependence upon the X source hierarchy.  After installation of the mit area
>of X, it should be possible to avoid having to use the MIT source hierarchy
>as part of the Imake process.  I mean, I have set up my symbolic links to
>/usr/bin/X11, etc.  Why do "contrib"uted programs have to rely on the core X
>source tree?

Have you tried using "xmkmf" a little script added by the standard installation
process that makes using Imakefiles even easier ? .. the comment for this
bourne script says ..

# generate a Makefile from an Imakefile from inside or outside the sources!

The normal installation process places a copy of all the configuration
files needed by imake into the lib directory that has been specified in the
mit/config/site.def file.

I use xmkmf to create makefiles for all the software that comes over on
comp.sources.x (including my own 8-) and it works perfectly.

Richard