|
@@ -17,7 +17,7 @@ Crypto related functions and helpers for [Swift](https://swift.org) implemented
|
|
|
|
|
|
## Sponsorship
|
|
|
|
|
|
-If you (or your Company) use this piece of work, please consider [Sponsorship](https://github.com/users/krzyzanowskim/sponsorship). This is the only option to keep the project alive. This is in your own best interrest.
|
|
|
+It takes some time to keep it all for your convenience, so maybe spare $1, so I can keep working on that. There are more than 8000 clones daily. If I'd get $1/month from each company that uses my work here, I'd say we're even. Hurry up, find the [Sponsorship](https://github.com/users/krzyzanowskim/sponsorship) button, and fulfill your duty.
|
|
|
|
|
|
CryptoSwift isn't backed by any big company and is developer in my spare time that I also use to as a freelancer.
|
|
|
|
|
@@ -112,7 +112,7 @@ It is recommended to enable [Whole-Module Optimization](https://swift.org/blog/w
|
|
|
You can use [Swift Package Manager](https://swift.org/package-manager/) and specify dependency in `Package.swift` by adding this:
|
|
|
|
|
|
```swift
|
|
|
-.package(url: "https://github.com/krzyzanowskim/CryptoSwift.git", .upToNextMinor(from: "1.3.1"))
|
|
|
+.package(url: "https://github.com/krzyzanowskim/CryptoSwift.git", .upToNextMinor(from: "1.3.2"))
|
|
|
```
|
|
|
|
|
|
See: [Package.swift - manual](http://blog.krzyzanowskim.com/2016/08/09/package-swift-manual/)
|
|
@@ -121,25 +121,6 @@ Notice: Swift Package Manager uses debug configuration for debug Xcode build, th
|
|
|
|
|
|
Notice: As of Swift 5.3, it's impossible to use Swift Package Manager to distribute binary (pre-compiled, optimized) version of CryptoSwift.
|
|
|
|
|
|
-#### XCFramework
|
|
|
-
|
|
|
-XCFrameworks require Xcode 11 or later and they can be integrated similarly to how we’re used to integrating the `.framework` format.
|
|
|
-Please us a script [scripts/build-framework.sh](scripts/build-framework.sh) to generate binary `CryptoSwift.xcframework` archive that you can use as a dependency in Xcode.
|
|
|
-
|
|
|
-CryptoSwift.xcframework is a Release (Optimized) binary that offer best available Swift code performance.
|
|
|
-
|
|
|
-<img width="320" alt="Screen Shot 2020-10-27 at 00 06 32" src="https://user-images.githubusercontent.com/758033/97240586-f0878280-17ee-11eb-9119-e5a960417d04.png">
|
|
|
-
|
|
|
-#### Embedded Framework
|
|
|
-
|
|
|
-Embedded frameworks require a minimum deployment target of iOS 9 or macOS Sierra (10.12). Drag the `CryptoSwift.xcodeproj` file into your Xcode project, and add appropriate framework as a dependency to your target. Now select your App and choose the General tab for the app target. Find *Embedded Binaries* and press "+", then select `CryptoSwift.framework` (iOS, macOS, watchOS or tvOS)
|
|
|
-
|
|
|
-
|
|
|
-
|
|
|
-Sometimes "embedded framework" option is not available. In that case, you have to add new build phase for the target.
|
|
|
-
|
|
|
-
|
|
|
-
|
|
|
#### CocoaPods
|
|
|
|
|
|
You can use [CocoaPods](https://cocoapods.org/pods/CryptoSwift).
|
|
@@ -151,6 +132,7 @@ pod 'CryptoSwift', '~> 1.0'
|
|
|
Bear in mind that CocoaPods will build CryptoSwift without [Whole-Module Optimization](https://swift.org/blog/whole-module-optimizations/) that may impact performance. You can change it manually after installation, or use [cocoapods-wholemodule](https://github.com/jedlewison/cocoapods-wholemodule) plugin.
|
|
|
|
|
|
#### Carthage
|
|
|
+
|
|
|
You can use [Carthage](https://github.com/Carthage/Carthage).
|
|
|
Specify in Cartfile:
|
|
|
|
|
@@ -160,7 +142,24 @@ github "krzyzanowskim/CryptoSwift"
|
|
|
|
|
|
Run `carthage` to build the framework and drag the built CryptoSwift.framework into your Xcode project. Follow [build instructions](https://github.com/Carthage/Carthage#getting-started). [Common issues](https://github.com/krzyzanowskim/CryptoSwift/issues/492#issuecomment-330822874).
|
|
|
|
|
|
----
|
|
|
+#### XCFramework
|
|
|
+
|
|
|
+XCFrameworks require Xcode 11 or later and they can be integrated similarly to how we’re used to integrating the `.framework` format.
|
|
|
+Please us a script [scripts/build-framework.sh](scripts/build-framework.sh) to generate binary `CryptoSwift.xcframework` archive that you can use as a dependency in Xcode.
|
|
|
+
|
|
|
+CryptoSwift.xcframework is a Release (Optimized) binary that offer best available Swift code performance.
|
|
|
+
|
|
|
+<img width="320" alt="Screen Shot 2020-10-27 at 00 06 32" src="https://user-images.githubusercontent.com/758033/97240586-f0878280-17ee-11eb-9119-e5a960417d04.png">
|
|
|
+
|
|
|
+#### Embedded Framework
|
|
|
+
|
|
|
+Embedded frameworks require a minimum deployment target of iOS 9 or macOS Sierra (10.12). Drag the `CryptoSwift.xcodeproj` file into your Xcode project, and add appropriate framework as a dependency to your target. Now select your App and choose the General tab for the app target. Find *Embedded Binaries* and press "+", then select `CryptoSwift.framework` (iOS, macOS, watchOS or tvOS)
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+Sometimes "embedded framework" option is not available. In that case, you have to add new build phase for the target.
|
|
|
+
|
|
|
+
|
|
|
|
|
|
##### iOS, macOS, watchOS, tvOS
|
|
|
|