Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!m.cs.uiuc.edu!flute.cs.uiuc.edu!totty
From: totty@flute.cs.uiuc.edu (Brian Totty)
Newsgroups: comp.windows.x
Subject: Imake For Other Projects Using X11
Message-ID: <1991Apr19.190034.23150@m.cs.uiuc.edu>
Date: 19 Apr 91 19:00:34 GMT
Sender: news@m.cs.uiuc.edu (News Database (admin-Mike Schwager))
Reply-To: totty@flute.cs.uiuc.edu (Brian Totty)
Organization: Picasso Group, DCS, University of Illinois, Urbana-Champaign
Lines: 32
Nntp-Posting-Host: flute.cs.uiuc.edu


	Have people come to a standard convention on how to build other
	(possibly complex) systems with imake?  I have read Paul DuBois'
	proposals about imake, which are the most detailed I have seen, but
	I was wondering what approach people have adopted if any.

	Specifically I would like:

	(1) The ability to search for templates in local, project specific
	    directories to override global config templates
	(2) New rules to propagate the new imake search path down through
	    subdirectories
	(3) Changes to xmkmf to initiate new imake search paths
	(4) Ability to handle X libraries in non-standard locations

	I can set up systems to do this by hand, but I do not want to edit the
	system files (so they don't get trashed with the next release of X),
	and I don't really want to insert lots of explicit #includes in
	subdirectory Imakefiles to find the right project templates.

	Do any people who work on the X build structure have comments about
	supporting this?  Do people already have a standard way of doing this?


							Thanks,

							--- Bri

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