home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!caen!saimiri.primate.wisc.edu!black-hole
- From: bin@primate.wisc.edu (Brain in Neutral)
- Newsgroups: comp.sys.sun.misc
- Subject: Re: Newbie Q: Using xmkmf w/ OpenView
- Date: 5 Nov 1992 09:26:53 -0600
- Organization: Cafe Limbo
- Lines: 21
- Sender: bin@uakari.primate.wisc.edu
- Message-ID: <1dbeftINNcff@uakari.primate.wisc.edu>
- References: <1992Nov5.075948.3792@ericsson.se>
- Reply-To: bin@primate.wisc.edu
- NNTP-Posting-Host: uakari.primate.wisc.edu
-
- From article <1992Nov5.075948.3792@ericsson.se>, by etxmesa@eos.ericsson.se (Michael Salmon):
- > guy@Auspex.COM (Guy Harris) writes:
- > [...]
- > |> (And yes, both "imake" and "xmkmf" come from the MIT X11 distribution;
- > |> that's where Sun got them.)
- >
- > Not quite, the Sun OW3.0 xmkmf is based upon the X11R5 xmkmf but it
- > includes a check to see if OPENWINHOME is defined. Unfortunately they
- > left off the -I so it doesn't work.
-
- I believe they also broke imake to make it difficult to specify
- where you want to look for configuration files, if you don't want
- to look in OPENWINHOME/config. You can get around this by setting
- the IMAKEINCLUDE environment variable to -Iwhere/you/want/to/look,
- but that's a hack. It makes configuration depend on something hidden
- in the environment (defeating one of the purposes of imake -- to make
- configuration explicit), and it makes it more difficult to switch
- between sets of configuration files.
- --
- Paul DuBois
- dubois@primate.wisc.edu
-