|
From: Dair G. <da...@re...> - 2004-06-28 22:07:37
|
Keith Wiley wrote: >First of all, of course, libraries are handled fairly differently in >Mach-O projects. I was unable to simply add the Quesa lib file to the >project and I don't know how to interpret the Quesa lib file as a >framework. It depends how you want to build it - if you want to build Quesa as a framework I believe the PB/Xcode projects have targets set up to do that. I don't know if they're set up to build static libraries: those work as you'd expect though, i.e., build a .lib file then just add it to your app project. >#if ((defined(__MWERKS__) && __dest_os =3D=3D __mac_os && !(__INTEL__)) ||= =20 >defined(MPW_CPLUS) || defined(MPW_C)) > #ifndef QUESA_OS_MACINTOSH > #define QUESA_OS_MACINTOSH 1 > #endif >#endif > >Any thoughts on how to kick-start Mach-O with Quesa? It sounds like your project isn't defining one of the build constants ahead of time, and so the auto-detection isn't picking up gcc. You can probably pull an appropriate test for gcc out of /usr/include/TargetConditionals.h >Fundamentally, I don't care too much about Mach-O, except that I >noticed that Queeg/Qut doesn't use Carbon events for Carbon >applications. It uses old fashioned Classic OS 9 events. The >preprocs in Queeg/Qut suggest that it only uses Carbon events for >Mach-O apps, not Carbon apps, as shown here at the top of Qut.c: This can probably be gutted to be honest, as we might as well use carbon events for any Carbon builds of Qut - the reason the WNE stuff was in there at all was to allow some of the apps to build as InterfaceLib apps (i.e., not Carbon) so they could also link to QD3D. >....which is why I'm trying to convert Queeg/Qut to Mach-O...although >I suspect I could approach the problem from the other direction and >try to get the Carbon version of Queeg/Qut to use Carbon events. The latter is probably the simplest approach, as there shouldn't anything stopping a Carbon build of Qut from using CE to get events. -dair ___________________________________________________ mailto:dair+refnum.com http://www.refnum.com/ |