Re: Source file names in binary
Re: Source file names in binary
- Subject: Re: Source file names in binary
- From: Thane Heninger <email@hidden>
- Date: Mon, 11 Jul 2005 11:09:49 -0600
If you look at /usr/include/assert.h, it indicates that when NDEBUG
is defined, assert(e) will be defined as ((void)0). If NDEBUG is not
defined, then assert(e) becomes a call to __assert() which includes
the __FILE__ and __LINE__ where the assert() function is called.
In other words, if it is assert that is adding your file names, then
try making sure that NDEBUG is defined for the preprocessor of the
compile. Stripping wouldn't remove it because once it's compiled, it
is a static character array, not a function name.
Thane
On Jul 11, 2005, at 3:10 AM, Duncan Wilcox wrote:
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.
"Deployment Postprocessing" only appears to do a strip, and I
should have mentioned that I tried stripping but the source file
names are still there. "Deployment Location" only appears to place
the app in /tmp/TextEdit.dst/Users/duncan/Applications/
TextEdit.app, but again, it still contains the source file names...
Other ideas?
Duncan
_______________________________________________
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