Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MPW, MAMake, Multiple folders of source, and Hell
Message-ID: <7957@hoptoad.uucp>
Date: 12 Jul 89 01:42:52 GMT
References: <4YialCi00UhW00uEYE@andrew.cmu.edu>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 37

In article <4YialCi00UhW00uEYE@andrew.cmu.edu> wb1j+@andrew.cmu.edu
(William M. Bumgarner) writes:
>Yes, once again, I am having difficulties with writing makefiles to my
>liking.  Only this time, I have complicated things a bit.
>
>What I want:  I want the MacAPP OOP to stay in one folder all by itself;
>fine this works.  I would like the C code to live in a seperate folder. 
>The big problem is that I want a MABuild mamake file that can deal with
>this.
>
>ipglue.c.o f ipglue.c # this doesn't work because the c code is not in
>the same folder with the make file
>
>ipglue.c.o f {CSrcDir}ipglue.c # this references the file fine, but
>doesn't use the MacAPP build stuff to compile the C-Code; it
>subsequently falls through and tells me it can't find ipglue.c.o
>
>I have tried a multitude of other things, including folder dependencies,
>and other archaic things with no luck.

o = :obj:
csrc = ':C source files:'

{o}ipglue.c.o	f	{csrc}ipglue.c
	{cc} {csrc}ipglue.c -o {o}ipglue.c.o

Any chance that this is a TCP/IP implementation I'm familiar with?
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com
Postal: 424 Tehama, SF CA 94103; Phone: (415) 495-2934

"A book is the product of a contract with the Devil that inverts the Faustian
 contract, he'd told Allie.  Dr Faustus sacrificed eternity in return for two
 dozen years of power; the writer agrees to the ruination of his life, and
 gains (but only if he's lucky) maybe not eternity, but posterity, at least.
 Either way (this was Jumpy's point) it's the Devil who wins."
	-- Salman Rushdie, THE SATANIC VERSES