Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!att!ucbvax!MEEPMEEP.PCS.COM!jkh From: jkh@MEEPMEEP.PCS.COM (Jordan K. Hubbard) Newsgroups: comp.windows.x Subject: Free Widget Set's missing Imakefile braindamage. Message-ID: Date: 10 Apr 91 12:19:30 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 26 X-Unparsable-Date: Wed, 10 Apr 91 14:23 MSZ A flame and a cautionary tale: From the README: > X includes & libs are located, then type make. I had Imakefiles > for these, but they didn't work right, so I switched to makefiles > for now... Arghhhh! No no no! The proper solution would have been to fix the Imakefiles or, at the very least, include them with the distribution so that others will a better grasp of Imakefile construction could have fixed them. As it is, people like myself who must support multiple architectures from the same source tree are out of luck. People: If you're going to distribute something, and have trouble with producing an Imakefile for it, ASK FOR HELP. DO NOT simply punt and send out a Makefile instead! Many of us have taken the Imakefile/config mechanism to its logical extension and can no longer use simple Makefiles without a lot of work - there are simply too many various flags and libraries involved on some machines. Thank you. Jordan