<div dir="ltr">I may be fundamentally misunderstanding the Windows Subsystem for Linux, but I believe it just provides binary compatibility for Linux x86_64 command-line tools, but doesn't quite implement enough of the Linux syscalls to run a Linux window manager in order to run GUI programs. So it's certainly something you could compile your server code for if you wanted to host on a Windows server, but it's not something you could use to distribute client software.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 3, 2016 at 9:11 AM, David Owens II <span dir="ltr"><<a href="mailto:david@owensd.io" target="_blank">david@owensd.io</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Historically, that's been true. However, I wonder if the new Linux subsystem work for Windows changes this. </div><div><br></div><div><a href="https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overview/" target="_blank">https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overview/</a></div><div><br></div><div>And further, will we need a check for this on Windows?</div><div><br></div><div>-David<br><br><div>Sent from my iPhone</div></div><div><div class="h5"><div><br>On May 3, 2016, at 9:07 AM, Michael Buckley via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">I wouldn't personally use a Cygwin or MinGW target these days, but I can see why a Cygwin target would be useful in a Swift context. I suspect most Swift code is either going to be written for iOS/Mac, or Linux server code, including third-party libraries. Lots of Swift code will probably have some POSIX calls that wouldn't otherwise be available on Windows.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 3, 2016 at 2:44 AM, hitstergtd+swiftevo--- via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Why is there a need to support Cygwin/MingW and their variants as a<br>
build target for Windows? MSVC is practically free these days.<br>
<br>
Doesn't supporting multiple different ABI targets on Windows just<br>
complicate matters unnecessarily? Isn't MSVC enough as a build target?<br>
<br>
I am not dejecting; rather, just wondering the actual need.<br>
<br>
On 3 May 2016 at 06:00, Sangjin Han via swift-evolution<br>
<div><div><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
> Hello swift-evolution,<br>
><br>
> This is continued from PR #2351(<a href="https://github.com/apple/swift/pull/2351" rel="noreferrer" target="_blank">https://github.com/apple/swift/pull/2351</a>).<br>
><br>
> Here is the brief history. (To avoid confusion, I used MSVC refer to<br>
> *-*-windows-msvc and Cygwin refer to *-*-windows-cygnus in LLVM.)<br>
><br>
> I needed the #if method to distinct MSVC from Cygwin, for mapping the Int to<br>
> CLongLong not CLong on MSVC.<br>
> In PR #2351, I simply added 'os(Cygwin)' and restrict 'os(Windows)' to<br>
> *-*-windows-msvc from *-*-windows-*, this solved my problem.<br>
><br>
> Jake(@jakepetroules) pointed out that Cygwin is not an OS and it will never<br>
> fixed to avoid breaking user applications.<br>
> There is more participants and opinions, briefly,<br>
> - introduce another new one such as 'env(cygnus)' or 'triple(Cygwin)'<br>
> - the usability of the common condition 'os(Windows)' for *-*-windows-*<br>
> - fundamentally, what do we gain from asking which os() is in use?<br>
> - 'env()' is too vague<br>
> - what the right questions?<br>
><br>
> Forgive me the poor quotations of valuable opinions.<br>
><br>
><br>
> I hope we find out the solution or method everybody satisfied.<br>
><br>
><br>
> -Han Sangjin<br>
><br>
</div></div>> _______________________________________________<br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
><br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></div></div></div></blockquote></div><br></div>