Re: Help! Has anyone compiled an external for OS X?
on 06.06.03 11:08 PM, [EMAIL PROTECTED] wrote: You *should* be able to add a target for a mach-o bundle and compile with the mach-o precompiled header in place of the Carbon, PPC, 68k, etc. You'll need to add frameworks (instead of libraries) to the target- i.e. Carbon.framework or others you may need such as Quicktime. Other than that, the example external code should compile into a bundle for you with little modification. Follow the install procedure from my previous email and you *should* be golden... With your encouragement, Brian, I will soldier on! Does the .bundle file go in the MacOS folder inside contents inside the .app? Can it? Should it? Must it? I *shall* succeed! (I gotta!) Thanks again, tereza + Tereza Snyder + Senior Software Developer + Attainment Company, Inc. + www.attainmentcompany.com + 800.327.4269 ___ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
Help! Has anyone compiled an external for OS X?
A year ago, I worked on an external for PPC and for Windows. I remember that getting everything right was a nightmare, but I succeeded in compiling, debugging, testing, installing, and deploying both using Codewarrior. Now I need to make a new external for Mac OS X and I find I'm completely at sea. The 2.5 readme says: Externals must now be in Mach-O bundle format on Mac OS X. Updated projects are included in the Mac OS X package. No such thing. I downloaded the external.sit file. I saw that there is a CodeWarrior project and I thought, halleluiah, there really is a project already set up! I'll be able to see what libraries are needed and where to put the output. I'm in business! If you've tried it, you know what I discovered. The external.proj doesn't have a mach-o target, only a Carbon, a 68K, a PPC, a Fat target. There are some mach-o files in the external Data folder, but CodeWarrior won't do anything with them. The readme is the same old readme. The tutorial is the same old tutorial (that requires you to compile the external before it will guide experienced 'C' programmers through the process of customizing a MetaCard external Huh!). The source files are the same old source files. Once upon a time I was an experienced 'C' programmer. There are half a dozen money-earning apps out there to prove it. But the compilers have changed and the OS has changed while I've been grinding out MetaCard apps. Has total immersion in MetaCard dulled my mind? I'm flummoxed. Can anyone out there start me off with a CodeWarrior project that's set up to produce a MetaCard external for MacOS X, and a little guidance as to where/how to put the output binary? I have both CW 7 and CW 8. Exasperated again, tereza + Tereza Snyder + Senior Software Developer + Attainment Company, Inc. + www.attainmentcompany.com + 800.327.4269 ___ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
Re: Help! Has anyone compiled an external for OS X?
Tereza, I haven't built an mach-o external with Codewarrior for quite a while, but what I DO have are several examples in ProjectBuilder. If you're interested, I'll send you a small one off-list. As far as outputting the binary, what you want to do is: 1) Compile your external code as a MacOS "bundle", i.e. "MyExternal.bundle". 2) Set the 'externals' property of your stack to the path to the bundle. This can be a relative path, just as with images / movies etc. 3) Quit and reload the stack HTH -- Brian Yennie Chief Technology Officer QLD Learning, LLC www.QLDLearning.com PH: (904)-997-0212 EMAIL: [EMAIL PROTECTED] ---
Re: Help! Has anyone compiled an external for OS X?
Well that's what I get for not looking first. Seems there is now a ProjectBuilder example in the external package. It looks like an oversight if the Mach-o target is missing from the CW project- there seems to be all the remnants of that target including settings and precompiled header files... unfortunately I don't have a machine with CW loaded at the moment to check it out. You *should* be able to add a target for a mach-o bundle and compile with the mach-o precompiled header in place of the Carbon, PPC, 68k, etc. You'll need to add frameworks (instead of libraries) to the target- i.e. Carbon.framework or others you may need such as Quicktime. Other than that, the example external code should compile into a bundle for you with little modification. Follow the install procedure from my previous email and you *should* be golden... HTH -- Brian Yennie Chief Technology Officer QLD Learning, LLC www.QLDLearning.com PH: (904)-997-0212 EMAIL: [EMAIL PROTECTED] ---
