I think what's going on here is that if you want to build a UB
version that targets 10.4 and later, make a bundle. If you want to
target 10.3 (or earlier) on PPC side, make a dylib.
Perhaps Jon can clarify, and/or perhaps we need a feature request,
but it might be neat if the PPC build of the plugin were used as the
first choice to build a PPC version of the app, which could be
backward compatible to 10.3 or 10.2 and so the plugin would be
packaged as a dynamic, while the UB version of the plugin would be
used to build the UB version of the app, which would require 10.4 and
so the plugin would be packaged as a bundle.
Make sense?
-Brad
On Feb 12, 2007, at 7:09 AM, Peter K. Stys wrote:
Thx Jon, got it: when I try this, my plugin fails to build, with Xcode
reporting:
powerpc-apple-darwin8-g++-4.0.1: -compatibility_version only allowed
with -dynamiclib
powerpc-apple-darwin8-g++-4.0.1: -compatibility_version only allowed
with -dynamiclib
Build failed (1 error)
works fine as a dylib.
what's up?
P.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
