<html><body><p><tt>phausler@apple.com wrote on 12/11/2015 12:02:30 PM:<br>> This is only tangentially related: but I was attempting to build <br>> dispatch as well to start work on CFRunLoop and a few other dispatch<br>> bound features in Foundation on linux. I was seeing similar failures<br>> as Dzianis Fedarenka. Is there a branch/fork that I can grab to test<br>> this stuff out w/ bringing stuff up in Foundation?</tt><br><br><tt>If you grab the master branch it should build libdispatch.so on ubuntu 15.04.</tt><br><br><tt>I've put a quick cheat sheet in a pull request: </tt><a href="https://github.com/apple/swift-corelibs-libdispatch/pull/11"><tt>https://github.com/apple/swift-corelibs-libdispatch/pull/11</tt></a><br><br><tt>There's a patch from Hubertus to get timers at least partially working that you may want too: </tt><a href="https://github.com/apple/swift-corelibs-libdispatch/pull/8"><tt>https://github.com/apple/swift-corelibs-libdispatch/pull/8</tt></a><br><br><tt><br>> My question is that of design and status of where things are at; <br>> CFRunLoop requires a method to interoperate with the main dispatch <br>> queue via _dispatch_get_main_queue_port_4CF and <br>> _dispatch_main_queue_callback_4CF. CFRunLoop will need to transact <br>> upon the same event source type as dispatch to ensure the main queue<br>> behaves correctly - so what type of event source should we be using?<br>> A socket? A producer/consumer notification via pthread conditions?</tt><br><br><tt>Sorry, I don't understand the code well enough yet to answer this one :( I'm sure Pierre or Daniel can.</tt><br><br><tt>--dave</tt><br><BR>
</body></html>