Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!torsqnt!tmsoft!robohack!woods From: woods@robohack.UUCP (Greg A. Woods) Newsgroups: news.software.b Subject: Re: Peter's gripes Summary: include's for make Message-ID: <1990Feb1.142615.29008@robohack.UUCP> Date: 1 Feb 90 14:26:15 GMT References: <519@smcnet.UUCP> <_E7166Cxds13@ficc.uu.net> <64T#Y$@rpi.edu> <7V716AAxds13@ficc.uu.net> <1990Jan29.232907.12180@utzoo.uucp> <1990Jan30.041541.23578@elroy.jpl.nasa.gov> <1990Jan30.185214.8197@utzoo.uucp> Organization: R. H. Lathwell Associates: Elegant Communications, Inc. Lines: 23 In article <1990Jan30.185214.8197@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes: > What is really wanted is some sort of #include facility for makefiles. > Which, of course, doesn't exist. I have some ideas for how to cope with > this, and you may see some movement in that direction soon. I've re-written the makefiles for 13-Nov-1989 C News to use include to a file containing most of the local configuration information (and use a new rule to create runnable versions of the now re-named .sh files by using a modified subst.) Now I have an advantage, since I'm running only SysV machines. SysV make has an 'include' statement. However, the BSD and other V7 derived versions of make should all be replaced by GNU-Make anyway! :-) (I use GNU-Make here in place of the distributed make for most things too.) Then again, /lib/cpp could be used ala GNU-Emacs. -- Greg A. Woods woods@{robohack,gate,tmsoft,ontmoh,utgpu,gpu.utcs.Toronto.EDU,utorgpu.BITNET} +1 416 443-1734 [h] +1 416 595-5425 [w] VE3-TCP Toronto, Ontario; CANADA