How to allow users of pre-built libraries step into code in the Xcode debugger?
How to allow users of pre-built libraries step into code in the Xcode debugger?
- Subject: How to allow users of pre-built libraries step into code in the Xcode debugger?
- From: Eric Wing <email@hidden>
- Date: Wed, 13 May 2015 15:34:59 -0700
This echoes similar sentiments to the recent thread, "How to
distribute & use a dynamic framework for iOS?".
I am distributing pre-built libraries for both OS X and iOS (dynamic
.frameworks on OS X and static .a libraries on iOS). The code is open
source, but echoing the sentiments of the other thread, there are lots
of really good reasons to distribute ready-to-go binaries.
But some times, it is really useful to be able to see into those
libraries in the debugger when debugging a problem. For dynamic
libraries, I know I can build a .dSYM and for static libraries, I can
compile debug symbols directly into the libraries.
But when actually debugging programs that use these libraries, I can
step into the associated source code on the machine that actually
compiled these libraries.
I want to allow some body else on a different computer who has
downloaded the source code, to be able to step into routines in the
Xcode debugger and see everything resolve, without them needing to
recompile all the libraries themselves and replacing mine.
I was hoping just having the Xcode project open on the library project
might make things 'just work', but that didn't work.
I would really appreciate any insights on how to make this work.
Thanks,
Eric
--
Beginning iPhone Games Development
http://playcontrol.net/iphonegamebook/
_______________________________________________
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