Peter O'Gorman wrote:
On
10/26/2009 02:07 PM, Kevin Brock wrote:
I haven't seen any information on how to make
Xcode *not* include these
load commands...
It's the compressed linkedit segment - see
http://developer.apple.com/mac/library/releasenotes/DeveloperTools/RN-dyld/index.html
Properly setting the deployment target is the solution.
It may help Mr. Limberg's problem. It's not the solution to all the
problems introduced by the LC_DYLD* commands.
If I build a framework for deployment target OS X 10.5, LC_DYLD_INFO
gets included. This isn't understood by some build tools on 10.5. In
particular, strip doesn't understand it, so if the framework is copied
anywhere by the project things break. (strip during copy is the
default
setting).
So setting the deployment target properly isn't really enough. If I
build a framework on 10.6 with default settings for deployment target
10.5, I can't go to a 10.5 system and link a project with it unless I
alter the defaults... It will load on 10.5, but can't be used as part
of another project in some cases.
Performing deployment post-processing on the framework helps, but that
isn't
the default, even in a release build.
The loader release notes you point at talk
about the fact that the new load command is going to be included, but
don't
address the build issues it introduces where people still need to do
some builds on 10.5.
Kevin