Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!rbarris
From: rbarris@orion.oac.uci.edu (Robert C. Barris)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacApp installation bites the dust
Summary: also in 'Startup' in MacApp folder
Keywords: MPW 3.2, MacApp, crash, disappointment, frustration, bitterness
Message-ID: <286900B7.19406@orion.oac.uci.edu>
Date: 26 Jun 91 21:01:43 GMT
References: <1991Jun26.154841.18646@cci632.cci.com> <1991Jun26.200234.11336@ux1.cso.uiuc.edu>
Distribution: usa
Organization: University of California, Irvine
Lines: 33

In article <1991Jun26.200234.11336@ux1.cso.uiuc.edu> ml27192@uxa.cso.uiuc.edu (Mark Lanett) writes:
>sdk@cci632.cci.com (Stephen Knight) writes:
>
>>Greetings,
>>  While trying to move up to MPW 3.2 Final, I've run into a snag when trying
>>to build the default MacApp.lib (actually, I started with our particular
>>settings and when that didn't work I shifted to .debug).
>
>>  After installing onto my disk from ETO #4 I tried:
>
>[lots of stuff deleted]
>
>That failure to compile has to do with a change Apple made to the NMRec
>structure in the 3.2 headers. You can always use the 3.1 ones.
>Also remember to include -pascal -clean on the MABuild line.
>
>--
>//-----------------------------------------------------------------------------
>Mark Lanett						mlanett@uiuc.edu
>Software Tools Group, NCSA


I also posted something about this and mentioned MacApp.lib.MAMake.
Wrong! There is a line in the {MacApp}Startup file which reads

# for compatibility with MPW 3.1 ( the currently released product )
# for MPW 3.2 or later remove or comment out the following line
SET MABuildDefaults "{MABuildDefaults} -d qMPW31=TRUE"

...so, I commented that line out and my builds worked again.

Rob Barris
rbarris@orion.oac.uci.edu