Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!julius.cs.uiuc.edu!flute.cs.uiuc.edu!totty
From: totty@flute.cs.uiuc.edu (Brian Totty)
Newsgroups: comp.windows.x
Subject: Re: Free Widgets
Message-ID: <1990Nov25.192219.7970@julius.cs.uiuc.edu>
Date: 25 Nov 90 19:22:19 GMT
References: <1990Nov24.230645.216@julius.cs.uiuc.edu> <6775@uceng.UC.EDU>
Sender: news@julius.cs.uiuc.edu (USENet News)
Reply-To: totty@flute.cs.uiuc.edu (Brian Totty)
Organization: Picasso Group, DCS, University of Illinois, Urbana-Champaign
Lines: 32


In article <6775@uceng.UC.EDU>, schriste@uceng.UC.EDU (Steven V.
Christensen) writes:
> 
> I would strongly suggest changing that from "makefile" to "Imakefile".
> It's not too hard to make an Imakefile for a small widget program.
> 
> 
	I did try to make Imakefiles for the system I have, but it was
	surprisingly difficult when you want to recursively make directories,
	build libraries, etc. because of conflicts with the X build defines.

	It would be nice to have a more strictly formalized list of what
	variables are for the X build and what variables are for using X
	components (the "out of source tree" builds).  Because of side effects
	it is tricky to steal some of the X build rules/defines for use in
	building your own project which happens to include some X stuff.
	If you try to build Imakefiles for a program that uses components
	from two other systems, each of which have their own Imakefiles, you
	are in for even more trouble.

	Any X build wizards who want to try their hands at designing a portable
	imake system for the Free Widgets distribution, which allows us to
	change configuration parameters, but is also compatible with X, are
	strongly encouraged to volunteer :-).

							--- Bri

   /                      Brian Totty              o o
  /__  __  o       1304 W. Springfield Avenue       o  
 /  / /   /             Urbana, IL 61801           \_/  "We have corn in
/__/ /   /             totty@cs.uiuc.edu                Massachusetts too!"