How do you build unified Production/Debug/Profile frameworks?
How do you build unified Production/Debug/Profile frameworks?
- Subject: How do you build unified Production/Debug/Profile frameworks?
- From: "E. Wing" <email@hidden>
- Date: Wed, 18 Jan 2006 17:57:10 -0800
I recently learned from here:
http://developer.apple.com/technotes/tn2004/tn2124.html
that many of the official OS X frameworks include debug and profile
variants inside and can be activated by defining the
DYLD_IMAGE_SUFFIX, e.g,
ls -l /System/Library/Frameworks/CoreFoundation.framework/Versions/A/
total 20024
-rwxr-xr-x 1 root wheel 1227724 Jan 16 21:04 CoreFoundation*
-rwxr-xr-x 1 root wheel 6564688 Dec 25 18:04 CoreFoundation_debug*
-rwxr-xr-x 1 root wheel 2454936 Dec 25 18:06 CoreFoundation_profile*
I would like to do this for my own frameworks. Is there an easy way to
set this up in Xcode?
Also, are there any tips and tricks/best practices you people
recommend for utilizing this with your own frameworks? For example if
you only want to run debug versions for only your own frameworks (and
not all System frameworks), would it make sense to have a symbolic
link to the "_debug" variant with a different suffix such as
"_mydebug".
Thanks,
Eric
_______________________________________________
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