Yes, I will be involved from the ground up which is why I'm trying to
figure out the best solution from start to finish.
Michael
On Jul 30, 2007, at 4:47 PM, Charles Yeomans wrote:
>
> On Jul 30, 2007, at 4:38 PM, Alfred Van Hoek wrote:
>
>>
>> On Jul 30, 2007, at 3:44 PM, Michael Williams wrote:
>>
>>> 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. ;)
>>
>> You leave that up to the RB developer who is using the plugin or
>> dylib. Your dylib (plugin) should be placed in the plugins folder at
>> the root of the REALbasic.app. The RB developer, when creating a
>> build using your dylib should then place the dylib into the framework
>> folder inside the app package. If you are creating a plugin (not a
>> dylib), REALbasic will handle all this under the hood. A plugin is
>> preferable, because realbasic "novices" don't need to go through the
>> hassle of incorporating a dylib, once the app is shipped...
>
>
> Actually, Michael is the Rb developer who is using the plugin or
> dylib.
>
> Charles Yeomans
> _______________________________________________
> 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>
|