Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
Stable way to embed open-source code into static library in iOS?
I am not sure if this question belongs here. Please instruct me if it does not.
I am building an SDK which has Reachability.h and Reachability.m files. If a user drops my code into his own, and if he has files with the same names, he will have to rename my files or his own for it to work. Is there an elegant way around this such that the SDK could always be dropped in without causing any conflicts?
If you’re providing source, then you can safely include Reachability (or whatever), but provide a target in the project file that doesn’t include them. If you’re providing a built library but not source code, then leave out the parts like Reachability that are readily available and provide instructions on how to get them and add them to the target project. Alternately, provide two (or more) versions of your library: one with Reachability and one without.