MMPR004@ECNCDC.BITNET (Scott Hutinger) (09/26/89)
Ah, Will this week continue? I seem to have problems all the time!! This time its MPW IIGS C 1.1B1. The problem is that I can write a small program in APW, and get a nice 32k file which works just fine. I compile and link the same program under MPW IIGS C, and the file is Much smaller, but has some internal stack problems. It looses the stack after a call to NoteOn. Actually after the return from the C function after NoteOn, as a call to another function after NoteOn works fine, but bombs at the return from the function which has NoteOn in it. Since the MPW IIGS version is so much smaller, I think I have a major problem. >mct mct.make > "{CIIGSLibraries}"Start.obj > mct.c.obj > LinkIIGS > "{CIIGSLibraries}"Start.obj > mct.c.obj > -lib "{CIIGSLibraries}"CLib > -o mct > DuplicateIIGS -mac mct : >mct.c.obj mct.make mct.c > CIIGS mct.c I also tried DirectIIGS and linked it in, but get the same problem. A smaller file that bombs. Could I possibly be missing something with the MPW IIGS linker? I also tried two segments, with main static, and the other dynamic, used DirectIIGS, but always get a smaller file that bombs out; except when compiled with APW. Scott Hutinger mmpr004@ecncdc.bitnet
MMPR004@ECNCDC.BITNET (Scott Hutinger) (09/26/89)
Ops, Make that MPW IIGS C 1.01 used with the older MPW IIGS tools, and the newer 1.1b1 tools. Could be I have missed linking in something other than start.obj first, and clib. But stackx.obj from the older version did not help either. Nor did direct.obj from the newer version of the tools. scott hutinger mmpr004@ecncdc.bitnet (the week is only starting...)