Newsgroups: comp.sys.mac.programmer
Path: utzoo!utgpu!cunews!bnrgate!bwdls61!usenet
From: aruigrok@bnr.ca (Adrian C Ruigrok)
Subject: MacApp C++ load/dump problem
Message-ID: <1991Feb21.202709.16319@bwdls61.bnr.ca>
Keywords: MacApp C++
Sender: usenet@bwdls61.bnr.ca (Use Net)
Organization: Bell Northern Research
Date: Thu, 21 Feb 1991 20:27:09 GMT

I have a baffling one that I am sure someone else must have come across.  It
has now happened on two seperate machines here.

The problem occurs when I build a MacApp program with different options (other
than -debug -sym) it does not build a new dump file.  But it still knows enough
to tell C++ to use the dump file on the compile.  The end result is that the
first file it tries to compile it gets an error because it can't find the dump
file it forget to create:
MABuildTool - v. 2.0.1 Release 10/25/90          Start: 3:27:03 PM 2/21/91

Copyright Apple Computer, Inc. 1986-1990
All Rights Reserved.

AutoSavingÉ
Target Folder: "Macintosh HD:MPW Folder:MailTool:.NoDebug Sym:"
Making:        MailTool.MAMake
Compiling:     UMailObjects.cp
can't open: Macintosh HD:MPW Folder:Load Files:.NoDebug Sym:UMacApp.h.dump
### MPW Shell - Execution of Macintosh HD:MPW Folder:MailTool:.NoDebug
Sym:MailTool.MakeIt terminated.
### MPW Shell - Execution of mabuild terminated.

I dug about and the MakeIt file has no reference to building the dump file as
it should.  I delete all references to the dump file, and recompiling with
-debug -sym builds the dump file like a charm.  -sym alone, or anything else
does not.  So somewhere it is getting in a state and I don't know how to get
around it.  For now I gave up on load/dump facility.
If you have seen this but never figured it out, drop me a line.  I will let you
know what I learned.
Thanks,
Adrian

---------------------------------
Adrian C Ruigrok
Bell-Northern Research
aruigrok@bnr.ca