Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!att!linac!uwm.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!ml27192
From: ml27192@uxa.cso.uiuc.edu (Mark Lanett)
Newsgroups: comp.sys.mac.programmer
Subject: MacApp under Sys 7
Message-ID: <1991Jun1.225934.7267@ux1.cso.uiuc.edu>
Date: 1 Jun 91 22:59:34 GMT
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 34

I want to point out a few problems people will have trying to run
MPW 3.2, and MacApp in particular, under System 7.

First, as we've already had discussed, you need the 3.2 Shell,
Linker, Lib tool, and DumpObj tool. It also comes with a new Choose
tool, but I don't think this is vital. SADE 1.1 and 1.2 won't work (a
relative statement, I realize), you need 1.3, currently only available as an
alpha version. And, no, it hasn't improved.

For MacApp there are other problems. Apple, in its infinite wisdom, went
around renaming some fields in structures in the 3.2 Includes*, so the MacApp
source won't compile. You must use the 3.1 Includes. It doesn't appear
to link with the 3.2 libraries, either, so I'm using the 3.1 stuff there
also. This is a problem because the MABuildTool will set up the link
with the 3.2 libraries if it detects the 3.2 shell (do you get the feeling
that someone at Apple wasn't testing things here?).

The only solution that works for me is to modify the MABuildTool source to
stop it from deleting the 3.1 library definitions. See line 1427 of
MABuildTool.p.  There's an if statement here that needs to be commented out
and replaced with "if false". You'll then have to recompile the MABuildTool,
a real trick if you have already converted to MPW 3.2 (!@#$) (How do I know,
you ask? Heh Heh). If you don't have Pascal and Asm, good luck. Maybe I could
figure out which bytes to change in the existing tool... Note: A possible
alternative to changing the MABuildTool would be changing the variable
definitions in Basic Definitions. I think I tried this and had no luck.

*I could see adding fields, maybe even renaming inappropriately named ones.
But changing NMRec.nmIcon to NMRec.nmSIcon? Give me a break.
--
//-----------------------------------------------------------------------------
Mark Lanett						ml27192@uxa.cs.uiuc.edu
Software Tools Group, NCSA				mlanett@ncsa.uiuc.edu
I'm not an idiot; I just play one on the net.