| Click here to select a new forum. |
| Compiling MacZoop: UPaintEngine.h |
Posted by: paws on 2023-03-05 02:41:30
I've been trying on and off to compile an example using the MacZoop framework, using CW5 and I've had a lovely old time learning about Universal Interfaces and pre-compiled headers and such. I'm down from about 2500 error messages (about 4 actual problems) to 56, and they seem to originate with a missing file called UPaintEngine.h, which does not appear to exist, neither on my drive nor on the internet. Does that mean anything at all to anyone here? |
Posted by: paws on 2023-03-05 03:29:16
This appears to be an unimportant dependency and I've just removed it. After a few linker things, I now have a MacZoop 2.5 project compiling with CodeWarrior.
It's an interesting developer experience. I code for a living and I'm a little embarrassed to see how useless I am without "jump to definition" or searchable docs... |
Posted by: Phipli on 2023-03-05 04:07:42
"jump to definition" Hum, when did CodeWarrior add that?
@cheesestraws? |
Posted by: cheesestraws on 2023-03-05 04:34:05
No idea, it's not a feature I (oddly) use very much... |
Posted by: paws on 2023-03-05 10:53:53
Do the later version have it? I settled on version 5 but I don't remember why. I think it seemed to be the last version that wasn't focused on the transition to OS X. |
Posted by: CC_333 on 2023-03-08 08:23:39
I settled on version 5 but I don't remember why. I think it seemed to be the last version that wasn't focused on the transition to OS X. There was a version that was the last to support 68k as a host (as opposed to a compiler target). Maybe it was 5?
EDIT: According to the Wikipedia article for CodeWarrior*, Pro 4 was the last version to support running on 68k, Pro 6 was last to support compiling 68k code, and Pro 8 was last to run on Classic Mac OS.
*As with any unverified source, take this with an appropriately sized grain of salt.
c |
| 1 |