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.

Sign up for GitHub

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

Jump to bottom

Swift Support #25

Open
sirinath opened this issue Aug 7, 2015 · 57 comments
Open

Swift Support #25

sirinath opened this issue Aug 7, 2015 · 57 comments

Comments

@sirinath
Copy link

sirinath commented Aug 7, 2015

Is it possible to support Swift also in a similar way?
@bhagyas
Copy link

bhagyas commented Aug 7, 2015

+1

@Inverness
Copy link

I assume this will come whenever the code for Swift is released.

@sirinath
Copy link
Author

sirinath commented Aug 7, 2015

Great. Is this definite?

@NSBrianWard
Copy link

I seem to recall in one of the talks they were giving about the bridge that they all but confirmed that it would eventually happen and then they sort of officially walked it back to "no comment."

Swift is the future of iOS development. There's no way that Microsoft won't eventually support it. If they don't, I'd imagine there's going to be enough code out there for someone to hack it all together between this project and Apple's Swift sources.

@MaddTheSane
Copy link

Also worth mentioning is that Swift will be open-sourced later this year. The ObjC-Swift bridging probably won't, though, so Microsoft would have to roll their own.

@James-Parsons
Copy link

+1

7 similar comments
@alfredobonino
Copy link

+1

@Tyratox
Copy link

Tyratox commented Aug 9, 2015

+1

@Lavender204
Copy link

+1

@jaredStef
Copy link

+1

@jamesmblair
Copy link

+1

@aluong-yammer
Copy link

+1

@agustingandara
Copy link

+1

@xGEKKOx
Copy link

xGEKKOx commented Aug 12, 2015

-1 Do not port swift please.

@jaredStef
Copy link

@xGEKKOx What possible cons for Windows developers are there? Why wouldn't you want to port Swift? It's going to be open source later this year as @MaddTheSane stated as well.

@vitalyster
Copy link

@BIGXmac so there is no need to make different, incomplete and buggy implementation, just wait Apple's release.
-1 too

@sirinath
Copy link
Author

When Apple open source Swift it will need to be ported to Windows as Windows is not included in the supported platform list.

@pierrejochem
Copy link

+1

@xGEKKOx
Copy link

xGEKKOx commented Aug 12, 2015

Obj c / C++ is good enough, we don't need swift. That's all.

@alfredobonino
Copy link

@xGEKKOx, YOU don't need swift!!!
I need swift.
+1

@James-Parsons
Copy link

@xGEKKOx you do understand that Apple wants to phase out Obj-C in favor for Swift.

@agustingandara
Copy link

@xGEKKOx ASM is good enough.
+1 to Swift.

@jakepetroules
Copy link
Contributor

The ObjC-Swift bridging probably won't, though, so Microsoft would have to roll their own.

Yes it will, it's part of Clang/LLVM, not a special separate tool. Not open sourcing it would be pointless additional work.

@kantorcodes
Copy link

There actually is a version of Swift for Windows.

http://www.elementscompiler.com/elements/silver/

The only downside is working with iOS/OSX requires you have a Mac on hand, but otherwise its pretty close to the real thing and works straight from visual studio.

@James-Parsons
Copy link

Sigh, If only Xamarin wasn't stupid expensive :(

@BlameOmar
Copy link

@mikenolimits The most vexing thing about Silver is that its String and Array are reference types instead of value types, so existing Swift code can't simply be recompiled and be correct. I suggest waiting for the near immediate Windows port once Apple open sources the compiler and standard library.

bdrlamb-ms added a commit that referenced this issue Sep 3, 2015
@bdrlamb-ms
Fix issue #25 - Implement UIBezierPath, make CAShapeLayer more robust
81e2110 
- Fix bugs in implementation of CGContextAddArc and CGContextClosePath
- Implement CGPathAddArc, fix bugs in CAPathAddEllipseInRect
- Make CAShapeLayer use a sublayer to position the rasterized path content
- Remove the bounds/position overrides in the compositor; these were needlessly complex and are no longer required now that CAShapeLayer uses sublayers to draw its contents
- Add XIB-based UIBezierPath/CAShapeLayer test page to WOCCatalog
@ananthunair
Copy link

seems apple is favouring swift more so swift support will be required for islandwood to stay in game

@OgnjenKop
Copy link

+1

@cfnp76
Copy link

cfnp76 commented Feb 26, 2016

💜💞❣

On 09/02/2559 BE, at 10:57 AM, Hanno notifications@github.com wrote:

+1

—
Reply to this email directly or view it on GitHub.

@DhaliwalX
Copy link

+1

@sirinath
Copy link
Author

sirinath commented Mar 9, 2016

Can something be done about this fast?

@b1lb0
Copy link

b1lb0 commented May 26, 2016

+1

4 similar comments
@sakrist
Copy link
Contributor

sakrist commented Jul 19, 2016

+1

@zhengying
Copy link

+1

@michaelversus
Copy link

+1

@jeeftor
Copy link

jeeftor commented Oct 26, 2016

👍

@sirinath
Copy link
Author

Can MS do something about this? Any information from the review?

@sirinath
Copy link
Author

Guys also see: https://twitter.com/Chris__Bailey/status/791333985649586176

But having said that it would be good if there are non cygwin solution also.

@pierrejochem
Copy link

Hey Guy's have a look here:

http://www.elementscompiler.com/elements/silver/default.aspx
https://swiftforwindows.codeplex.com/
https://github.com/tinysun212/swift-windows/releases/tag/swift-msvc-20160418

I'm quite sure this will getting forward!

@nazrdogan
Copy link

+1

1 similar comment
@cherepets
Copy link

+1

@James-Parsons
Copy link

Over a year later and nothing. I think it's safe to say that we're not getting it.

@bredov
Copy link

bredov commented Nov 28, 2016

With some recent activity on apple/swift (swiftlang/swift#5904 and others) it seems windows (MSVC) support may land into official repository in several months.

Will Swift be considered to be supported by winobjc project after it gains full support for building on windows?

@sakrist sakrist mentioned this issue Dec 19, 2016
Closed
@gruve-p
Copy link

gruve-p commented Jan 6, 2017

+1

@jack-guy
Copy link

jack-guy commented Mar 6, 2017

It appears Windows support for Swift is a go. That should have been the last blocker on support for this, right?

@ad1Dima
Copy link

ad1Dima commented Jun 16, 2017

@Harangue it support compile Linux binaries om windows. Not windows binaries unfortunately.
https://github.com/apple/swift/blob/master/docs/Windows.md#windows-subsystem-for-linux-wsl

@privet56
Copy link

+1

1 similar comment
@mhuusko5
Copy link

mhuusko5 commented Aug 4, 2017

+1

@DHowett-MSFT DHowett-MSFT mentioned this issue Oct 23, 2017
Open
@ndcg91
Copy link

ndcg91 commented Dec 29, 2017

+1

@MSFTFox MSFTFox mentioned this issue Mar 1, 2018
Closed
@ConanNobita
Copy link

+1

@DHowett-MSFT DHowett-MSFT mentioned this issue May 29, 2018
Closed
@mubaris
Copy link

mubaris commented Oct 25, 2018

Any update on building a Swift bridge?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests