What exactly are the steps? I'm not familiar with creating framework bundles. Do I compile the library externally first, then copy the "dylib" into the Framework Bundle and create? Or do I drag all of the source into the Framework Bundle, then compile it all? How do I make RB aware of the framework bundle? Is it something that the end user is still going to have to install anyway? As you can tell, I'm rather lost. ;)
Regards, Michael On Jul 30, 2007, at 1:28 PM, Charles Yeomans wrote: > For Mac OS X, you can put the .dylib into the bundle, and this is a > good way to do it. I think that you can wrap the library into a > framework bundle, and this should make it easier to declare to it > without hard-coded paths. > > Charles Yeomans > > > On Jul 30, 2007, at 1:16 PM, Michael Williams wrote: > >> Gotcha, >> >> So you're recommending going the "dylib" route as opposed to the >> plugin route? What kind of recommendations have you for actually >> distributing the "dylib"? Someone mentioned actually placing the >> "dylib" in the RB package, I'm not terribly familiar with that >> process, nor how to reference a self-contained library. >> >> Michael >> >> On Jul 30, 2007, at 12:23 PM, Charles Yeomans wrote: >> >>> I looked at the link. The library has a C interface, so my guess is >>> that it would be fairly straightforward to write some REALbasic >>> wrapper code that would allow you to call the library from all >>> platforms. >>> > > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
