0

I am creating an 'SDK' which will enable communication with a piece of custom hardware (via BLE, abstracting my comm protocol to async methods/callbacks, on various classes all Obj-C). I wish to package this SDK so I can distribute it to users so they can build apps using this hardware. I want to provide an .h file(s) and a pre-compiled library (closed-source).

What's the best practice here? Shall I choose to create a .framework, .a, .dylib? what's the difference between them and their usage cases? what's the correct way to create the needed library?

many thanks

Tommy Devoy
  • 13,441
  • 3
  • 48
  • 75
mindbomb
  • 1,642
  • 4
  • 20
  • 35

1 Answers1

0
  1. You cannot create dylib for iOS. User cannot link his project with that library dynamically on iOS, it is platform restrictions.
  2. You can create framework or .a file (static library).
  3. There can be some issues with resources from you library (framework)
  4. It is dublicate question, see Difference between framework and static library in xcode4, and how to call them
Community
  • 1
  • 1
BergP
  • 3,453
  • 4
  • 33
  • 58
  • what issues with resources from framework? So should I go for .a or .framework? couldn't find answers in the so-called duplicate question – mindbomb Oct 08 '13 at 16:28
  • This answer has been **deprecated** and should be updated after iOS 8 age. – Itachi Dec 30 '16 at 06:55