[swift-dev] Build failure for Linux: "No such module: SwiftGlibc"

I’m trying to cross-compile Swift for the Raspberry Pi. I’ve got the tools and most of the standard library compiling, but I’m getting stuck trying to build the platform components for Glibc. Swift is just complaining that the “SwiftGlibc” module doesn’t exist. I’d appreciate it if anybody could

Re: [swift-dev] Build failure for Linux: "No such module: SwiftGlibc"

> On 22 Apr 2016, at 06:46, Timothy Wood wrote: > > >> On Apr 19, 2016, at 1:57 AM, Karl Wagner via swift-dev > <mailto:swift-dev@swift.org>> wrote: >> >> I’m trying to cross-compile Swift for the Raspberry Pi. I’ve got the tools >> and most of th

Re: [swift-dev] Build failure for Linux: "No such module: SwiftGlibc"

> On 2 May 2016, at 18:42, Joseph Bell wrote: > > Karl, > > A number of us are on Slack working with ARM support - would you like an > invite? > > Joe > Hi, yes that would nice. The modulemap issue can be fixed by adding a -resource-dir flag. Going with a comment in AddSwift.cmake, I sw

Re: [swift-dev] Build failure for Linux: "No such module: SwiftGlibc"

> On 3 May 2016, at 20:12, Jordan Rose wrote: > > >> On May 3, 2016, at 10:40, Karl Wagner via swift-dev > <mailto:swift-dev@swift.org>> wrote: >> >> >>> On 2 May 2016, at 18:42, Joseph Bell >> <mailto:j...@iachieved.it>> wro

[swift-dev] Cross-compiling (nearly) everything for RPi from OSX

I’ve managed to cross-compile the swift tools for the Raspberry Pi from OSX. I thought I’d share my changes. Branch is here: https://github.com/karwa/swift . I’ll work on merging it soon. The only real change we need is a bit more structure to the install location

Re: [swift-dev] Cross-compiling (nearly) everything for RPi from OSX

> On 10 May 2016, at 04:11, Karl Wagner wrote: > > I’ve managed to cross-compile the swift tools for the Raspberry Pi from OSX. > > I thought I’d share my changes. Branch is here: > https://github.com/karwa/swift . I’ll work on > merging it soon. > > The only

Re: [swift-dev] How to run the tests out-of-tree?

> On 13 May 2016, at 02:36, Greg Parker wrote: > > >> On May 12, 2016, at 7:45 AM, Karl via swift-dev > > wrote: >> >> So I’ve been working on cross-compiling for ARM, and it seems pretty good - >> only a bit of refactoring of the build script really needed. It’s a

Re: [swift-dev] How to run the tests out-of-tree?

“installable". Karl > On 13 May 2016, at 03:40, Dmitri Gribenko wrote: > > On Thu, May 12, 2016 at 6:33 PM, Karl Wagner via swift-dev > wrote: >> My original idea was a lot simpler - create a script grabbing the specific >> executables we need (FileCheck, llvm-link

Re: [swift-dev] [Foundation] Remove/disable availability declarations on OSX? What to do with them?

Yeah it all makes much more sense now. I was so stuck in the terminal I completely forgot there even was an Xcode project. So I’ll submit a patch making the python script farm out to xcodebuild instead of trying to configure a Mac. > On 18 May 2016, at 16:35, Philippe Hausler wrote: > > Yea,

Re: [swift-dev] SwiftGlibc: Use VFS overlay instead of -fmodule-map-file

I’m not sure if we could dynamically generate the YAML because of multiarch, and because the GCC triple isn’t always the same as the LLVM triple. For example, you might built ‘armv7-linux-gnueabihf’ for Swift/LLVM, but GCC only has ‘arm-linux-gnueabihf’. But yeah, thats a really good find, it’

Re: [swift-dev] Open-source toolchains for Playgrounds (iOS, Xcode 8)

I’m not sure that’s the reason: - Only Playgrounds are restricted, not Apps. You can still use OSS toolchains to build apps, like you always could. - You can only submit to the AppStore from the latest stable Xcode (7.3, isn’t it?) - You can also deploy apps by manually building & installing wit

Re: [swift-dev] [RFC] Finer grained OS checks

My thoughts: I don't like the idea of additional qualifiers after OS. Perhaps we could rename it something more generic like "SDK" or split the non-common stuff in to a seprarate module? As for the proposal (I know it's too late for Swift 3, but I read it so I might as well say what i thought ab

Re: [swift-dev] [RFC] Finer grained OS checks

> > > > On Jul 11, 2016, at 9:50 AM, Karl Wagner via swift-dev > > mailto:swift-dev@swift.org)> wrote: > > > > > > > > > > - Also don't like the simulator condition variable. The iOS simulator is > > literally x86 iOS.

Re: [swift-dev] Endgame for Swift 3

https://github.com/apple/swift-evolution/tree/master/proposals/0092-typealiases-in-protocols.md Isn't half of this done, or something? I seem to remember seeing code about it, and I think there may even be a hidden switch to enable what is there. Sent from my new Email (ht

Re: [swift-dev] Proposal: Opaque SIL values

> On 24 Jan 2017, at 20:10, Andrew Trick via swift-dev > wrote: > > I’m sending out a proposal for fundamentally changing SIL. This work feeds > into generic code optimization, resilience, semantic ARC, and SIL ownership. > This was discussed at length back in October—some info went out on >

Re: [swift-dev] Resilient dynamic dispatch ABI. Notes and mini-proposal.

> On 3 Feb 2017, at 03:57, Andrew Trick via swift-dev > wrote: > > I'm following up on a resilient dynamic dispatch discussion kicked off by > Slava during a performance team meeting to summarize some key > points on public [swift-dev]. > > It's easy to get sidetracked by the details of dynami

[swift-dev] swift.org nightlies are old

It looks like the nightlies on swift.org haven’t been uploading properly for some time now. The latest toolchain from master is dated April 26th. Could somebody look in to it? Thanks - Karl ___ swift-dev mailing list swift-dev@swift.org https://lists.

Re: [swift-dev] swift.org nightlies are old

ed tomorrow. > > > On May 7, 2017, at 8:49 PM, Karl Wagner via swift-dev > > wrote: > > > > It looks like the nightlies on swift.org haven’t been uploading properly > > for some time now. The latest toolchain from master is dated April 26th. >

Re: [swift-dev] What can you change in a non-exhaustive enum?

> On 30. Sep 2017, at 20:23, Xiaodi Wu via swift-dev > wrote: > > On Sat, Sep 30, 2017 at 11:58 AM, > wrote: > Message: 2 > Date: Fri, 29 Sep 2017 18:21:44 -0700 > From: Jordan Rose mailto:jordan_r...@apple.com>> > To: swift-dev mailto:swift-dev@swift.org>>

Re: [swift-dev] What can you change in a non-exhaustive enum?

> On 4. Oct 2017, at 01:37, Karl Wagner wrote: > > > >> On 30. Sep 2017, at 20:23, Xiaodi Wu via swift-dev > > wrote: >> >> On Sat, Sep 30, 2017 at 11:58 AM, > > wrote: >> Message: 2 >> Date: Fri, 29 Sep 2017 18:21:44 -0700 >>

Re: [swift-dev] [swift-evolution] Re-pitch: Deriving collections of enum cases

Personally, I think this dovetails quite nicely with the ‘random’ discussion. Enums are just one kind of type with a finite set of values; Int and Bool also fit that description, as may many structs and even classes. Having a general way to express that would be quite nice, IMO. - Karl > On 9.

Re: [swift-dev] Conditional conformance: Removing the opt-in flag

> On 22. Dec 2017, at 07:13, Ted Kremenek via swift-dev > wrote: > > > >> On Dec 19, 2017, at 9:39 PM, Ted Kremenek via swift-dev > > wrote: >> >> >> >> On Dec 19, 2017, at 8:57 PM, Douglas Gregor > > wrote: >> >>> >>> >>> Sent from

Re: [swift-dev] Make offset index available for String

Swift used to do this, but we switched it around so indexes couldn’t self-increment. One of the problems was that strings are value-types. So you would get an index, then append stuff to the string, but when you tried to advance the index again it would blow up. The index retained the backing,