<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">It is better in general, yes.<div class=""><br class=""></div><div class="">However, there are details that make having a separate repo desirable. Think of it more as a place for arm-specific patches to get merged in very quickly and easily while the official swift PR system is running. </div><div class=""><br class=""></div><div class="">Because arm (32-bit specifically) is such an odd duck relative to the other platforms, we sometimes ask for changes that may increase the risk to other, supported, platforms. Those changes can take months to merge into the official repo, if at all. We had been working from individual repos (mostly mine), and that was a nightmare when people tried to build for themselves, as everything was constantly in flux.<div class=""><br class=""></div><div class="">In response, we ended up creating our own org that has a stable fork of the official sources that we could coordinate around, provide stable instructions for, and not worry about how long patches can take to merge into the official channels.</div><div class=""><br class=""></div><div class="">The swift team has been great to work with, but their risk calculus is necessarily different than ours.</div><div class=""><br class=""></div><div class="">- Will</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 10, 2016, at 10:48 AM, Kostiantyn Koval <<a href="mailto:konstantin.koval1@gmail.com" class="">konstantin.koval1@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Will<div class=""><br class=""></div><div class="">Thanks for your great work on arm support. Wouldn't it be better if ARM support was added directly to the Apple swift repo. </div><div class="">I'm not sure if it's currently possible and what technical challenges we would need to solve to achieve it, i just wold like to know if it has been discussed with swift team?</div><div class=""><div class="">
<div class=""><br class=""></div><div class="">- Kostiantyn</div>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On 10 Oct 2016, at 18:30, william via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Ron,<div class=""><br class=""></div><div class="">As the unofficial maintainer of Swift on Arm, I can say with confidence that there is no official anything about Swift on Linux/ARM. :)</div><div class=""><br class=""></div><div class="">That said, Swift works and builds fantastically well on the TK1 (which I use as my primary development platform).</div><div class=""><br class=""></div><div class="">Also, yes, all official Swift platforms are 64-bit, and that causes some issues occasionally in user code and libraries when people fail to consider 32-bit systems. Swift and it's libraries, however, all work with 32-bit just fine. Any issues I've hit in other places have been pretty trivial.</div><div class=""><br class=""></div><div class="">I have spent some time in the past on the Nvidia TX1, with 64-bit userspace, and I did get swift somewhere resembling a working state, but it was a little flaky in some parts.</div><div class=""><br class=""></div><div class="">Finally, there is a swift-arm github organization with a set of repos that lag considerably from the mainline, but represent a stable port to arm. It's currently at the Swift 3.0 release. Additionally, there is a swift-arm slack team that you are welcome to join:</div><div class=""><br class=""></div><div class=""><a href="http://dev.iachieved.it:9909/" class="">http://dev.iachieved.it:9909</a></div><div class=""><br class=""></div><div class="">cheers,</div><div class="">- Will</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Oct 10, 2016, at 8:54 AM, Ron Olson via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi all-<br class=""><br class="">Is there any "official" place to check what the state of Swift on Linux/ARM is? Specifically, what HW platforms/distro combinations have working binaries? I've seen blogs about getting it compiled and working on Raspberry PIs, but they seem to have caveats as well as general surprise they got it to work at all.<br class=""><br class="">I'm trying to compile Swift on an Nvidia TK1 board, which is an arm7+gpu soc running 32-bit Ubuntu 14, and before I delve too deeply into it (getting some linker errors), I'm wondering if I should bother; I've read that Swift is for 64-bit processors only, but then I read about getting it working on a Raspi where no 64-bit distro is available, AFAIK, so hence my confusion about what 'works' and what doesn't.<br class=""><br class="">Thanks for any info,<br class=""><br class="">Ron<br class="">_______________________________________________<br class="">swift-dev mailing list<br class=""><a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class="">https://lists.swift.org/mailman/listinfo/swift-dev</a><br class=""></div></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">swift-dev mailing list<br class=""><a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class="">https://lists.swift.org/mailman/listinfo/swift-dev</a><br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></body></html>