On Feb 17, 2007, at 2:03 PM, Norman Palardy wrote:
On Feb 17, 2007, at 1:33 PM, Tim Jones wrote:
On Feb 17, 2007, at 10:24 AM, Norman Palardy wrote:
On Feb 17, 2007, at 9:46 AM, Tim Jones wrote:
Since I have the same plugin dylibs in the GUI project's
folders, and the Resources.rsrc seems to be empty, is it safe to
copy ONLY the testtool binary? It seems to work in simple
tests, but then again, testtool is a very simple tool that uses
the MBS folder-finder functions and then just prints "testtool
works" and exits, so I'm concerned that more advanced tools
might need something that isn't in the GUI Project's hierarchy.
Anyone have the scoop on this?
As long as you've used the same versions of RB & MBS to create
everything you should be ok to just copy the testtool binary
This doesn't appear to be the case. It turns out that RB renames
the plugin dylib files between builds. This results in an odd,
ownerless dialog popping up to tell you that plugin functions
can't be accessed.
That's a change
I've done exactly this with older RB versions (not 2007r1)
In My test, the MBS Main dylib was named _22.136.dylib wthe
version compiled into the tool was named _36.135.dylib. Also, I'm
finding MULTIPLE Main and Mac dylibs in my GUI app. Is THAT normal?
Christian explained this. It's not caused by renaming of the dylib,
these parts are various components of the plugin, so the numbers are
normal. Therefore, the answer to the original question turns out to
be "it's probably best to copy the plugin parts over from the Lib
folder to the GUI app's Frameworks folder unless you're absolutely
sure that the plugin segments used in teh Console app are also used
in the Desktop app."
Tim
--
Tim Jones
[EMAIL PROTECTED]
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
