On Feb 26, 2007, at 04:00 UTC, Harry Morris wrote: > Thanks! It looks like the problem was lack of Quesa. Interesting > that it kept the program from compiling, rather than producing a run > time error.
Yes, the IDE needs the plugin to load, and the plugin needs Quesa. It didn't use to be that way, and there's really no reason it should be that I can think of. Indeed, many of the services that plugin provides (basic Vector3D math, for example) shouldn't need Quesa at all. I believe there's a bug report/feature request to restore this to the previous state of running (in a limited fashion) without Quesa around, but I don't know the feedback ID. But it may be related to this one: <http://www.realsoftware.com/feedback/viewreport.php?reportid=zbmmbaqc> > Putting Quesa in place didn't help until I closed the > project and reopened it. I'm very surprised you didn't have to restart the IDE! > The problem is that as a beginner PEF and Mach-O mean nothing to me. > I suspect it has to do with Intel vs PowerPc, or maybe between OS X > and OS 9? Ah, I see. OK, here's the deal in a nutshell: there are two formats for executable (application) files on the Mac: PEF, which is a modern, sensible format that the Mac has always used up until recently, and Mach-O, which is an older, more primitive format that Steve Jobs used at NeXT and then foisted onto the rest of us when he returned to Apple and came out with OS X (which is just NeXT in a Mac's clothing in many other ways, too). PEF apps can run on OS 9 and OS X, but they can only contain PowerPC code. Mach-O apps only run on OS X, but they can contain either PowerPC or Intel code. So, unfortunately, since modern Mac hardware is Intel, we have to use the Mach-O format, which means your apps won't run on OS 9 anymore. Mach-o apps also make declares differently, as this error message was pointing out. See <http://www.declaresub.com/ideclare/>, an excellent online book by Charles Yeomans, for everything you ever wanted to know about declares (and more!). > My best guess would be that it's a Intel vs PowerPC thing, but > setting the build settings to Mac OS PowerPC still gives an error. > So I'm confused. Yeah, the build settings are confusing. But rather than mucking with them, just search and replace "CarbonLib" with "Carbon" and I bet you'll be better off (and then you can build for Intel, though not for OS 9). Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
