From: Allison N. <dem...@ma...> - 2009-01-08 15:57:35
|
Hi Brian, Maybe I've misunderstood your question, but here's my understanding of things: If you are writing you're own .m file, you just make sure that it is all encapsulated in an Objective-C class, rather than using standard C. The RubyCocoa bridge then handles the objective-C class automatically. I don't know if I'm telling you something you already know, but if you have an Objective-C class, you just add its source files (.m/.h) to your RubyCocoa project, and XCode compiles them automatically for you, and you can access them from Ruby the same way you access any Cocoa classes. Hope that helps, Alli On Thursday, January 08, 2009, at 04:16PM, "Brian Marick" <ma...@ex...> wrote: >I have a tiny .m file that I use for testing. I create a bundle from it: > > `cc -o #{basename}.bundle -bundle -framework Foundation >#{basename}.m` > >Is there a way to get metadata for that file without building a >framework? gen_bridge_metadata(1) has an example of creating metadata >from -lcurl, but I can't make it work for my .m and .h file. Should I >keep digging or give up? > >----- >Brian Marick, independent consultant >Mostly on agile methods with a testing slant >www.exampler.com, www.exampler.com/blog, www.twitter.com/marick > > >------------------------------------------------------------------------------ >Check out the new SourceForge.net Marketplace. >It is the best place to buy or sell services for >just about anything Open Source. >http://p.sf.net/sfu/Xq1LFB >_______________________________________________ >Rubycocoa-talk mailing list >Rub...@li... >https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk > > |