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

On Mon, May 9, 2016 at 7:11 PM, Karl Wagner via swift-dev wrote: > Does anybody (or any bots) install directly from the build script? Yes, that's how all Swift builds are done. Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j*/ ___ swift-dev mailing list

Re: [swift-dev] [SR-710][RFC] Automatically detecting XCTest test methods on Linux: Reflection? SourceKit?

> On May 9, 2016, at 7:35 PM, Brian Gesiak wrote: > > Thanks for the feedback, everyone! > > Porting SourceKit to Linux seems like a reasonable solution to me. Still, > there are 354 lines of code in tools/SourceKit that reference "XPC", so a > Linux port will take more than a few lines of so

Re: [swift-dev] [SR-710][RFC] Automatically detecting XCTest test methods on Linux: Reflection? SourceKit?

On Mon, May 9, 2016 at 7:35 PM, Brian Gesiak wrote: > Thanks for the feedback, everyone! > > Porting SourceKit to Linux seems like a reasonable solution to me. Still, > there are 354 lines of code in tools/SourceKit that reference "XPC", so a > Linux port will take more than a few lines of source

Re: [swift-dev] [SR-710][RFC] Automatically detecting XCTest test methods on Linux: Reflection? SourceKit?

Or maybe not, looks like there’s a Unix transport in transports/unix.c. > On 10 May 2016, at 1:48 PM, Luke Howard via swift-dev > wrote: > > There is libxpc from NextBSD: > > https://github.com/NextBSD/libxpc > > You’d still need to implement Mach IPC on to

Re: [swift-dev] [SR-710][RFC] Automatically detecting XCTest test methods on Linux: Reflection? SourceKit?

There is libxpc from NextBSD: https://github.com/NextBSD/libxpc You’d still need to implement Mach IPC on top of something though. — Luke > On 10 May 2016, at 12:35 PM, Brian Gesiak via swift-dev > wrote: > > Thanks for the feedback, everyone! > > Porting

Re: [swift-dev] swift (ABI) and Windows

> On May 9, 2016, at 7:19 PM, Saleem Abdulrasool wrote: > > On Sat, May 7, 2016 at 7:55 PM, Sangjin Han wrote: > One more, > > I couldn't build the libswiftCore.dll which can be used for Hello.swift. At > least one symbol _TMSS is not dllexported. > (But I could build the dll with dlltool.exe

[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] [SR-710][RFC] Automatically detecting XCTest test methods on Linux: Reflection? SourceKit?

Thanks for the feedback, everyone! Porting SourceKit to Linux seems like a reasonable solution to me. Still, there are 354 lines of code in tools/SourceKit that reference "XPC", so a Linux port will take more than a few lines of source code changes. I imagine we'll need to insert some sort of shi

Re: [swift-dev] swift (ABI) and Windows

On Sat, May 7, 2016 at 7:55 PM, Sangjin Han wrote: > One more, > > I couldn't build the libswiftCore.dll which can be used for Hello.swift. > At least one symbol _TMSS is not dllexported. > (But I could build the dll with dlltool.exe which make all symbols to be > dllexported) > > To find out the

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1259

Fixed. Thanks! > On May 9, 2016, at 6:29 PM, Michael Ilseman wrote: > > Expired password? > > WARNING: Your password has expired. > Password change required but no TTY available. > Build step 'Execute shell' marked build as failure > > >> On May 9, 2016, at 6:28 PM, no-re...@swift.org

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1259

Expired password? WARNING: Your password has expired. Password change required but no TTY available. Build step 'Execute shell' marked build as failure > On May 9, 2016, at 6:28 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-package-linux-ubuntu-15_10 [#1259] > > Build URL: > https:

[swift-dev] New Swift snapshots available!

New Swift snapshots available! Download new packages from https://swift.org/download/ Swift Development: (master) Following repository are tagged with swift-DEVELOPMENT-SNAPSHOT-2016-05-09-a https://github.com/apple/swift

Re: [swift-dev] LazyFilterCollection is not a Collection

On Mon, May 9, 2016 at 11:46 AM, Rob Napier wrote: > It violates the performance requirements. > CollectionType.count requires O(1) access if Index is a > RandomAccessIndexType. Hi Rob, We don't have RandomAccessIndexType anymore. Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j*/

[swift-dev] LazyFilterCollection is not a Collection

(Continuing a discussion from https://twitter.com/cocoaphony/status/729712476451971073.) The current recommendation for converting from lazy to strict is with an Array constructor: Array(xs.lazy.) Because the Array constructor accesses count and then iterates over the sequence, this generall

Re: [swift-dev] Consider removing the space in Swift AST dump's "decl" attribute?

On Mon, May 9, 2016 at 10:00 AM, Minsheng Liu wrote: > Thanks for your information. However, what I intend to work on is a > Swift-to-JS translator, which I guess probably need to stick with the > upstream anyway. I think that make the output a bit more parsing-friendly > will not harm, will it?

Re: [swift-dev] Consider removing the space in Swift AST dump's "decl" attribute?

> On May 9, 2016, at 10:00 AM, Minsheng Liu via swift-dev > wrote: > > Thanks for your information. However, what I intend to work on is a > Swift-to-JS translator, which I guess probably need to stick with the > upstream anyway. I think that make the output a bit more parsing-friendly > wil

[swift-dev] TWISt-shout Newsletter 2016-05-09

Here is your TWISt-shout newsletter for the week of 2016-05-02 to 2016-05-08 https://github.com/pepperdog/TWISt-shout/blob/master/2016/TWISt-shout-2016-05-09.md Enjoy! -Kenny ___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mail

Re: [swift-dev] swift (ABI) and Windows

> On May 7, 2016, at 4:01 PM, Sangjin Han wrote: > > Hi all, > > I merged Saleem's #2080 to my working branch, and did some experiment. > > I could compile easily Hello.swift with #2080 merged one. > > swiftc -c -o Hello.obj Hello.swift > clang -o Hello.exe Hello.obj -llibswiftCore -llibs

Re: [swift-dev] Consider removing the space in Swift AST dump's "decl" attribute?

Thanks for your information. However, what I intend to work on is a Swift-to-JS translator, which I guess probably need to stick with the upstream anyway. I think that make the output a bit more parsing-friendly will not harm, will it? Moreover, if you do not suggest parse the dumped AST, is there

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 14.04 (master) #1265

I’ll have a look. > On May 9, 2016, at 9:27 AM, Daniel Dunbar wrote: > > +Todd > > This looks like lldb failures? > > ERROR: test_lldbmi_break_insert_function_pending > (tools/lldb-mi/breakpoint/TestMiBreak.py) > ___ swift-dev mailing list swift-

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1250

This is a configuration issue; Mishal and I will work it out. > On May 9, 2016, at 00:41, Daniel Dunbar via swift-dev > wrote: > > I can't tell what failed here: > > > YEAR:2016 > MONTH:05 > DAY:09 > TOOLCHAIN_VERSION:swift-DEVELOPMENT-SNAPSHOT-2016-05-09-a > ARCHIVE_DIR:swift-DEVELOPMENT-SNA

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 14.04 (master) #1265

+Todd This looks like lldb failures? Issue Details = ERROR: test_lldbmi_break_insert_function_pending (tools/lldb-mi/breakpoint/TestMiBreak.py) UNEXPECTED SUCCESS: test_Hc_then_Csignal_signals_correct_thread_launch_llgs (tools/lldb-server/TestLldbGdbServer.py) UNEXPECTED SUCCESS: tes

Re: [swift-dev] Consider removing the space in Swift AST dump's "decl" attribute?

On Sun, May 8, 2016 at 8:22 PM, Minsheng Liu via swift-dev wrote: > Hi, > > I notice that currently the dumped AST contains a parsing-unfriendly “decl” > attribute like this: >> decl=fib.(file).func decl.b@fib.swift:4:9 Dumped AST is not meant to be machine parseable. The format is subject to ch

[swift-dev] Consider removing the space in Swift AST dump's "decl" attribute?

Hi, I notice that currently the dumped AST contains a parsing-unfriendly “decl” attribute like this: > decl=fib.(file).func decl.b@fib.swift:4:9 The “func decl” contains a space but has nothing like a quote around it. The whole AST output is delimited by spaces. I think this might create some diff

Re: [swift-dev] Why are we re-linking?

I've updated the code to make that behavior optional and controllable: https://github.com/rintaro/swift/commit/bfac557 Revision from only lib/, include/, and tools/: utils/build-script -RT --reconfigure \ --swift-vc-revision-include-dir="lib;include;tools" Revision from whole repository exclu

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1250

I can't tell what failed here: YEAR:2016 MONTH:05 DAY:09 TOOLCHAIN_VERSION:swift-DEVELOPMENT-SNAPSHOT-2016-05-09-a ARCHIVE_DIR:swift-DEVELOPMENT-SNAPSHOT-2016-05-09-a-1229 ./clang: 9f0d189 ./llbuild: 0702f53 ./swift_integration_tests: 98f6c6d ./llvm: dffa09f ./swift: de7ef4b ./swiftpm: b26305a ./