> On Dec 11, 2015, at 9:02 AM, Philippe Hausler via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > > This is only tangentially related: but I was attempting to build dispatch as > well to start work on CFRunLoop and a few other dispatch bound features in > Foundation on linux. I was seeing similar failures as Dzianis Fedarenka. Is > there a branch/fork that I can grab to test this stuff out w/ bringing stuff > up in Foundation? > > My question is that of design and status of where things are at; CFRunLoop > requires a method to interoperate with the main dispatch queue via > _dispatch_get_main_queue_port_4CF and _dispatch_main_queue_callback_4CF. > CFRunLoop will need to transact upon the same event source type as dispatch > to ensure the main queue behaves correctly - so what type of event source > should we be using? A socket? A producer/consumer notification via pthread > conditions?
The linux equivalent to what we’re doing for the runloop is to use an eventfd() to replace sending messages to its port. >> On Dec 11, 2015, at 8:27 AM, David P Grove via swift-corelibs-dev >> <swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org>> wrote: >> >> swift-corelibs-dev-boun...@swift.org >> <mailto:swift-corelibs-dev-boun...@swift.org> wrote on 12/11/2015 11:19:15 >> AM: >> > >> > The linux port is in progress, and even if it built, right now, it >> > wouldn’t be functional. >> > >> > -Pierre >> > >> > Yes. I completely understand that there linux port is not >> > functional. So I want to contribute to it. But it's practically >> > impossible since there is no usable build system :(. >> >> It's limping along. We've managed to run a few programs successfully. >> >> I think the next step is actually to get the test suite to compile & build >> so we can see what functionally isn't working yet. >> >> Pierre and Daniel, we could use some guidance on how to approach this. The >> tests have quite a few unguarded includes of mach header files, uses of mach >> types, and includes of Foundation. How would you like this porting to >> proceed? Hubertus has already done some initial poking at it, but getting >> direction on the intended outcome would be very helpful. >> >> thanks, >> >> --dave >> >> >> _______________________________________________ >> swift-corelibs-dev mailing list >> swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev >> <https://lists.swift.org/mailman/listinfo/swift-corelibs-dev> > > _______________________________________________ > swift-corelibs-dev mailing list > swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org> > https://lists.swift.org/mailman/listinfo/swift-corelibs-dev > <https://lists.swift.org/mailman/listinfo/swift-corelibs-dev>
_______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
