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: turn off mpw 3.1 compat. switch
Keywords: MPW 3.2, MacApp, crash, disappointment, frustration, bitterness
Message-ID: <2868F921.15237@orion.oac.uci.edu>
Date: 26 Jun 91 20:29:21 GMT
References: <1991Jun26.154841.18646@cci632.cci.com>
Distribution: usa
Organization: University of California, Irvine
Lines: 29

In article <1991Jun26.154841.18646@cci632.cci.com> sdk@ccird2.UUCP (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:
>
>>directory "compilers:developer:macapp folder:libraries"
>>mabuild -debug macapp.lib
>
>and the following appeared (sorry about the runon lines :( ):
>
>>MABuildTool - v. 2.0.1 Release 10/25/90          Start: 11:27:07 AM 6/26/91

<many compile errors deleted>
I ran into this too. You need to disable MPW 3.1 compatibility
(note the references to $IFC qMPW31 all over the place).
This is easy to do, just take a look at the MacApp.lib MAMake file
(at least I think that's where it was) and there is one line you need
to comment out. This is in the manual too, but of course I didn't find
that until later.
What happened is that the header files were "cleaned up" a bit from MPW
3.1 to 3.2... the MacApp source knows this but that conditional compilation
was still set up for 3.1 when you tried to build it. It does work...
I hope this helps.

Rob Barris
rbarris@orion.oac.uci.edu