Post marked as solved
Click to stop watching this thread.
You have stopped watching this post. Click to start watching again.
contentPostList.repliessolved.tooltip
Thanks for your response eskimo.Would you be so kind and elaborate on how to build a Cocoa Touch Framework for iOS from multiple existing static libraries? Is that possible?To be more precise, I actually have a folder structure for the static libraries that looks like this:root/
|----lib_1/
|----lib/
|----1.a
|----2.a
|----include/
|----1.h
|----2.h
|----lib_2/
|----lib/
|----1.a
|----2.a
|----include/
|----1.h
|----2.h
|----lib_3/
|----lib/
|----...
|----include/
|----...
|----...All of the headers and libraries need to be included into the framework. The wrapper wraps around all those libraries.Why? Create a separate project for your wrapper makes things more complex, and it’d be best to avoid that unless absolutely necessary.Well, as I tried to explain, it'd be great if I could build a framework that includes the wrapper and the static library with the corresponding headers (althouth, if I got you correctly, I'd have to build at least two frameworks for both iOS and iOS Simulator as they're different platforms -- assuming I use Xcode 10).