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

Swift 3.0 Support #33

Closed
PranayDMI opened this issue Jul 25, 2016 · 11 comments
Closed

Swift 3.0 Support #33

PranayDMI opened this issue Jul 25, 2016 · 11 comments
Assignees

Comments

@PranayDMI
Copy link

This is not working with the XCode 8.0 & Swift 3.0. Its not compiling with Swift 3.0.

@nlutsenko
Copy link
Member

We don't yet support Swift 3.0, but we are planning to add it the moment Swift 3.0 goes GM.
As for right now - I would recommend either using a Migration Assistant to migrate to Swift 3.0.

@nlutsenko nlutsenko changed the title Not working with XCode 8.0 & Swift 3.0 Swift 3.0 Support Jul 25, 2016
@nlutsenko nlutsenko self-assigned this Jul 25, 2016
@nlutsenko
Copy link
Member

This said, we have Swift 2.3 support, which adds support for Xcode 8 on current master (thanks to #27) and release with it is coming soon.

@nlutsenko
Copy link
Member

@augene, @PranayDMI, just released BoltsSwift 1.2.0, which has support for Xcode 8 and Swift 2.3.
I suggest you guys give it a spin and comment here if it still fails for you (in that case, would love to know your setup, since it works great via Carthage and subproject on a test project).

@mobitronics
Copy link

It's pretty weird, that was the compilation issue due to the wrong syntax. I used the XCode 8.0 default migration tool.
Now its working fine with XCode 8.0 & Swift 3.0.
Thanks @nlutsenko.

@simonnarang
Copy link

I'm using Xcode 8.0 with swift 3.0 and trying to import via carthage

/Carthage/Build/iOS/BoltsSwift.framework/BoltsSwift compiled with older version of Swift 
language (2.0) than previous files (3.0) for architecture x86_64 clang: error: linker 
command failed with exit code 1 (use -v to see invocation)

Anyone seen this error before?

@nlutsenko
Copy link
Member

@simonnarang, I would recommend trying to migrate the framework to Swift 3.0 in your own custom fork using built-in migration assistant from Xcode.

@simonnarang
Copy link

Okay thanks

@nlutsenko
Copy link
Member

nlutsenko commented Aug 1, 2016

Hey folks,

Since we have an Xcode beta 4 from this morning - I've just went ahead and migrated the entirety of our sources to current latest Swift 3.0 that comes in the beta.

It lives in this branch. If you are curious or want to use to use the alpha version of Bolts-Swift in Swift 3.0 - I would recommend checking it out.

Please comment here if you run into any issues.
Our stake on supporting Swift 3.0 remains the same - the moment Swift 3.0 goes GM together with Xcode 8.0 - we'll migrate to it and will cut a release.

@fedetrim
Copy link

@nlutsenko last week, Xcode 8 GM was released. Is there any update on this issue?

@clayellis
Copy link

Xcode 8 has been released, is anyone actively working on the update? @nlutsenko

@nlutsenko
Copy link
Member

Hey guys, frankly, am a quite tangled in other things this week, but am going to try my best to get to this by end of this week. Stay tuned for news and look for incoming PRs.

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

6 participants