Re: Source file names in binary
Re: Source file names in binary
- Subject: Re: Source file names in binary
- From: Chris Espinosa <email@hidden>
- Date: Sun, 10 Jul 2005 09:19:20 -0700
On Jul 10, 2005, at 1:46 AM, Duncan Wilcox wrote:
Hi there, I just signed up, hopefully this isn't a FAQ (looked in the
archives and googled around a bit).
I understand that using __FILE__-using macros (like assert) will
produce a filename constant string, but I don't have asserts in all
sources (and I kill asserts in deployment builds), so there's
something else generating the source file name.
For example:
strings /Applications/TextEdit.app/Contents/MacOS/TextEdit | grep \\.m
shows no source file, but if I build TextEdit from the sample code
(xcode 2.1 on Tiger, with an upgraded project file) the source file
names are indeed visible:
/Users/duncan/Desktop/TextEdit copy/Document.m
/Users/duncan/Desktop/TextEdit copy/DocumentReadWrite.m
/Users/duncan/Desktop/TextEdit copy/Controller.m
/Users/duncan/Desktop/TextEdit copy/ScalingScrollView.m
/Users/duncan/Desktop/TextEdit copy/MultiplePageView.m
/Users/duncan/Desktop/TextEdit copy/Preferences.m
/Users/duncan/Desktop/TextEdit copy/EncodingManager.m
What magic build option do I have to set to prevent source file names
from being output to the final binary?
Try "Deployment Postprocessing" (and set "Deployment Location" too).
These are normally used only when you do an xcodebuild install from the
command line, but you can set them on your routine Deployment or
Release builds, too.
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