Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!wb1j+
From: wb1j+@andrew.cmu.edu (William M. Bumgarner)
Newsgroups: comp.sys.mac.programmer
Subject: MPW, MAMake, Multiple folders of source, and Hell
Message-ID: <4YialCi00UhW00uEYE@andrew.cmu.edu>
Date: 11 Jul 89 21:53:18 GMT
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 32

Yes, once again, I am having difficulties with writing makefiles to my
liking.  Only this time, I have complicated things a bit.

The environment:  MPW, MacAPP, and a program involving not only MacAPP
OOP, but also C and TCP/IP code.

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.

Why I can't do it:  Ok, the OOP is happy enough sitting in the directory
that I have it (with the mamake file).  But, I have yet to find a way to
reference the C-Code as a dependency...

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.

Help me!  I'm going insane with this one.

BTW: the fact that TCP/IP code is used doesn't really matter
BBTW: We are using MPW v3.0 and MacAPP v2.0b9...

b.bum
wb1j+@andrew.cmu.edu