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 protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
