Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!psuvax1!ukma!sean
From: sean@ms.uky.edu (Sean Casey)
Newsgroups: news.software.b
Subject: Re: Configuring make (Re: Peter's gripes)
Message-ID: <13955@s.ms.uky.edu>
Date: 3 Feb 90 15:21:00 GMT
References: <519@smcnet.UUCP> <KARL.90Jan18224915@tut.cis.ohio-state.edu> <_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> <1 <Csi
Organization: The Leaning Tower of Patterson Office @ The Univ. of KY
Lines: 16

|In article <Csic,52@cs.psu.edu> flee@shire.cs.psu.edu (Felix Lee) writes:
|>Systems I know let you say something like
|>	make -f ../conf/make.defs -f ./Makefile
|>This is flexible enough to handle mildly complex configuration
|>problems.  Are there systems where this will not work?

This is precisely the system I use for large software packages.

I stole the idea from the MMDFII sources.

Sean
-- 
***  Sean Casey          sean@ms.uky.edu, sean@ukma.bitnet, ukma!sean
***  "May I take this opportunity of emphasizing that there is no cannibalism
***  in the British Navy. Absolutely none, and when I say none, I mean there
***  is a certain amount, more than we are prepared to admit." -MP