home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!uvaarpa!cv3.cv.nrao.edu!laphroaig!cflatter
- From: cflatter@nrao.edu (Chris Flatters)
- Newsgroups: comp.unix.bsd
- Subject: Re: Naive "imake" questions
- Message-ID: <1992Aug16.213304.24358@nrao.edu>
- Date: 16 Aug 92 21:33:04 GMT
- References: <1992Aug16.160342.11490@NeoSoft.com>
- Sender: news@nrao.edu
- Reply-To: cflatter@nrao.edu
- Organization: NRAO
- Lines: 27
-
- In article 11490@NeoSoft.com, karl@NeoSoft.com (Karl Lehenbauer) writes:
- >OK, lots of X programs come with Imakefiles and need imake to generate
- >a customized Makefile for the local machine.
- >
- >Firing up imake as distributed in X386 for 386BSD, it complains about
- >not being about to find "Imake.tmpl". I found that setting the env
- >var IMAKEINCLUDE to "-I/usr/lib/X11/config" would get it to create
- >makefiles OK, but not with quite the correct information to build
- >the target, like library paths are wrong.
- >
- >Is there another place this is supposed to point to, to get to the right
- >stuff? If not, is there a copy or link that needs to be done? Otherwise,
- >what is the accepted way to set this up?
-
- You need to run imake as follows
-
- imake -DUseInstalled -I/usr/lib/X11/config
-
- Most X11 installations have a script called xmkmf that invokes imake with
- the correct flags. I don't know if this is present in X386 for 386BSD.
-
- There is also the possibility that you need to edit /usr/lib/X11/config/site.def
- to reflect your particular installation but this is very unlikely if you followed
- a standard installation procedure.
-
- Chris Flatters
- cflatter@nrao.edu
-