Path: utzoo!attcan!uunet!lll-winken!ames!vsi1!wyse!mips!synthesis!len
From: len@synthesis.Synthesis.COM (Len Lattanzi)
Newsgroups: comp.windows.x
Subject: Re: Set of fixes to contrib ...
Message-ID: <11166@mips.mips.COM>
Date: 14 Jan 89 02:48:49 GMT
References: <16592@lll-winken.LLNL.GOV>
Sender: news@mips.COM
Reply-To: len@synthesis.synthesis.com (Len Lattanzi)
Organization: Synthesis Software Solutions Inc, Sunnyvale, CA
Lines: 41

In article <16592@lll-winken.LLNL.GOV> casey@lll-crg.llnl.gov (Casey Leedom) writes:
:  Just how do you use imake and Imakefiles when all you've got are
:installed libraries and include files???  My suggestions to the X
:Consortium along those lines are: 1. install imake itself as part of the
:installation process into your BINDIR.  2. Provide a simple define,
:switch, whatever, to easily configure your Makefiles to compile within or
:outside the X tree ala:
:
:	% make Makefile IMAKEDEFS="-DCompileWithInstalled"
:
:or some such.  In fact, since most development is done with installed
:libraries, etc. I think that should be the default and the other should
:be an option. (IMAKEDEFS="-DMakeWorld"?)
:
:Casey

What's wrong with having your own IMAKEINCLUDE environment variable
with the following diff to Imake.tmplate
434c434
<             TOP = TOPDIR
---
>             TOP = .
459,463c459,463
<            XLIB = $(XLIBSRC)/libX11.a
<          XMULIB = $(XMUSRC)/libXmu.a
<         OLDXLIB = $(OLDXLIBSRC)/liboldX.a
<        XTOOLLIB = $(TOOLKITSRC)/libXt.a
<          XAWLIB = $(AWIDGETSRC)/libXaw.a
---
>            XLIB = /usr/lib/libX11.a
>          XMULIB = /usr/lib/libXmu.a
>         OLDXLIB = /usr/lib/liboldX.a
>        XTOOLLIB = /usr/lib/libXt.a
>          XAWLIB = /usr/lib/libXaw.a

This is unix specific but you get the idea.

-Len
 Len Lattanzi (len@Synthesis.com) <{ames,pyramid,decwrl}!mips!synthesis!len>
 Synthesis Software Solutions, Inc.				1 408 991 0367
 292 Commercial Avenue, Sunnyvale, California 94086