Re: Problems with executable file size
Re: Problems with executable file size
- Subject: Re: Problems with executable file size
- From: Brant Sears <email@hidden>
- Date: Thu, 14 Dec 2006 13:35:23 -0500
Thank you for this tip. Checking Deployment Postprocessing reduces
the app bundle from 30 MB to 2 MB which is great.
However, when I try to launch, The application crashes. I see the
message "Link (dyld) error: lazy pointer not found" in the error
report. When I try to launch in the debugger, I'm seeing mangled
names that refer to dyld. So, I'm guessing that symbols that should
be loaded dynamically are not being loaded correctly.
Anyone know off hand what this is all about?
On Dec 14, 2006, at 1:16 PM, Chris Espinosa wrote:
On Dec 14, 2006, at 9:46 AM, Brant Sears wrote:
Hi. I have an application that is larger than I expected in
Release builds. However, the release builds are the same size as
debug builds. I suspect that my project file is misconfigured.
My application imports several static libraries in the form of .a
archives.
Is there a way to examine the binary application and libraries to
tell whether debug symbols are present? (Like a command line tool
for this?)
1) Switch your Debug Information Format to "Dwarf with dSym". Your
debugging symbols will be stored in a separate file, making your
release executable smaller.
2) Check "Deployment Postprocessing". This performs additional
stripping steps normally done only when installing, such as dead
code stripping.
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden