Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] A template to make universal dynamic framework #203

Open
dodikk opened this issue Oct 27, 2014 · 3 comments
Open

[feature] A template to make universal dynamic framework #203

dodikk opened this issue Oct 27, 2014 · 3 comments

Comments

@dodikk
Copy link
Contributor

dodikk commented Oct 27, 2014

AS a Library vendor
I WANT a project template that produces fat binaries
SO THAT I can easily distribute them to my customers

As of xCode6, the built-in framework produces binaries for either of

  • Device only
  • Simulator only

See the log below

dodikk$ pwd
/Users/dodikk/Library/Developer/Xcode/DerivedData/HelloSwiftFramework-gcglkmozajqrsidsqtfcewuujygs/Build/Products/Debug-iphonesimulator/HelloSwiftFramework.framework

dodikk$ ls
Headers         HelloSwiftFramework Info.plist      Modules


dodikk$ file HelloSwiftFramework 
HelloSwiftFramework: Mach-O 64-bit dynamically linked shared library x86_64
@dodikk
Copy link
Contributor Author

dodikk commented Oct 27, 2014

As apple's framework uses dynamic libraries under the hood. For this reason it requires linking the static lib dependencies into it.

So I think, this repo should not be retired since

  1. Static frameworks are still a good option for code sharing
  2. Some lipo create scripts are still required to produce a single dynamic framework binary for both the device and the simulator.

@AlexDenisov
Copy link

@dodikk, 👍
I'm still using iOS-Universal-Framework, because new frameworks work only for iOS8.

@dodikk
Copy link
Contributor Author

dodikk commented Oct 27, 2014

It's not apple's largest problem. Here are a few more :

  1. Xcode does not build fat frameworks (for both device and simulator).
  2. Xcode frameworks are dynamic while "most libs out there" are static which causes conflicts and dependency management challenges.
  3. No idea how apple frameworks are going to work with cocoapods due to (2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants