On Nov 14, 2011, at 9:47 AM, Nathan Sims wrote: > Now, I go to create a 'Cocoa Library' project in Xcode 3.2.6, and it > generates a libaaa.h and a libaaa.m for me. But in the .m file, there's an > '@implementation libaaa' line. I'm confused, I thought a Cocoa library was a > number of *.o (compiled .m files) archived into a single file with a transfer > vector table at the front.
Yes… and this is one of the .m files that will make up your library. It sounds like you are getting the library and the source files mixed up? (For one thing, the source files don’t have to be named “libaaa”. You can rename them whatever you want if that’s clearer to you.) > I'm unclear on what its expecting me to put in the libaaa.m '@implementation' > area. Do I ignore it? libaaa.a isn't a class, so why does it have an > @implementation? Just because that’s what’s in the template for this project type. Don’t worry about it. If you don’t want to put a class in there, just erase what Xcode put in. —Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
