-
Notifications
You must be signed in to change notification settings - Fork 525
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
Swift 3.0 compatible branch #216
Comments
I've created this fork that should get you at least to compile: or via pods pod 'Cartography', :git => 'https://github.com/solomon23/Cartography.git', :branch => '3.0' |
Thanks @solomon23. It compiles and, at least in my usage of it, also works fine! 👍 |
@solomon23 nice! |
I have have problem with converting to the latest Swift 3 syntax I use "pod 'Cartography', :git => 'https://github.com/solomon23/Cartography.git', :branch => '3.0'" to install Cartography |
Hi @GP000 looks like that fork hasn't been updated to the latest Swift 3.0 syntax. Try my fork instead, which I'm using in a shipping app:
I haven't tried using it with CocoaPods (I use Carthage) but it should be fine. |
Sorry, closed the issue by mistake 😊 . Re-opened. |
Just looking at your screenshot more, I can't see the full error but it looks like it's saying |
There is an active PR for 3.0 #228 would recommend using that instead |
it is an empty project with only Cartography imported via pods |
Swift 3.0 support is now in 1.0 💯 |
When I import cartography onto my project I get this error. Module compiled with Swift 3.0 cannot be imported in Swift 3.0.1: /Carthage/Build/iOS/Cartography.framework/Modules/Cartography.swiftmodule/arm64.swiftmodule |
Yep - binaries only work on a specific version of Swift. Any minor swift changes requires a new binary. |
I know it's very early days, but any idea when a branch migrated to Swift 3 will be available? Anyone depending on this lib (or any other Swift libs) is currently stuck not being able to build their projects with Xcode 8 until all dependent libs are also migrated to Swift 2.3 or 3.0 (preferable).
The text was updated successfully, but these errors were encountered: