On Jun 26, 2006, at 11:03 AM, Ruslan Zasukhin wrote:
At least I'd like express hope, that REAL will send (may be private)
notification to plugin developers at least 1-2 weeks before you ship
REALbasic UB.
We have our beta program that will be used to test the feature, as it
is for every other feature.
Using V4RB MACHO -- we have
plugin + macho dylibs.
When REALbasic produce compiled app, we put dylibs inside of package,
And this require correction of executable_path. This work fine for
RELEASE.
But we have not found any way to make V4RB MACHO to work for DEBUG
builds in
REALbasic....So V4RB users for now use in development V4RB CARBON, and
if
they want they do RELEASE build using V4RB MACHO.
And source of problem is that RB is CARBON PEF, so it cannot work
correctly
with MACHO dylibs.
It sounds like even if the IDE were Mach-O, there would still be the
problem that the dylibs aren't being copied into the debug application.
Why don't you statically link in whatever the dylib contains? This
would make life much easier for your users, not requiring to modify
their application packages every time they build.
HTH,
Jon
--
Jonathan Johnson
REAL Software, Inc.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
