We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
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
The text was updated successfully, but these errors were encountered:
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
lipo create
Sorry, something went wrong.
@dodikk, 👍 I'm still using iOS-Universal-Framework, because new frameworks work only for iOS8.
It's not apple's largest problem. Here are a few more :
No branches or pull requests
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
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
The text was updated successfully, but these errors were encountered: