The proper fix is to have a shell script phase that makes a copy of
the
original .a and runs ranlib on the copy; then link your target against
the copy instead of the original. Set the script phase's input and
output files correctly, and the script will only run once, or
whenever a
new version of the .a comes down from cvs.
In my experience, Xcode ignores the output files of shell script
phases as far as feeding them back into the rules system is concerned
(i.e., it only uses them to determine whether the script should run,
but doesn't attempt to compile/link whatever you specify as output).
So my question is: how do you make Xcode link against the copy of the
library you make in the shell script?
Thanks,
Jonas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
