<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">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?</div><div class=""><br class=""></div><div class="">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?</div><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 11, 2015, at 8:27 AM, David P Grove via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><p class=""><tt class=""><a href="mailto:swift-corelibs-dev-bounces@swift.org" class="">swift-corelibs-dev-bounces@swift.org</a> wrote on 12/11/2015 11:19:15 AM:</tt><br class=""><tt class="">> <br class="">> The linux port is in progress, and even if it built, right now, it <br class="">> wouldn’t be functional.</tt><br class=""><tt class="">> <br class="">> -Pierre</tt><br class=""><tt class="">> <br class="">> Yes. I completely understand that there linux port is not <br class="">> functional. So I want to contribute to it. But it's practically <br class="">> impossible since there is no usable build system :(.</tt><br class=""><br class=""><tt class="">It's limping along. We've managed to run a few programs successfully. </tt><br class=""><br class=""><tt class="">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.</tt><br class=""><br class=""><tt class="">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.</tt><br class=""><br class=""><tt class="">thanks,</tt><br class=""><br class=""><tt class="">--dave</tt><br class="">
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=0mkChau6XnFV-2FCNUik62L9ZaldD0W0ziOwj-2F3jLx368Ywjhx8n8v-2BKiqHEV32gcTMftIMI-2BO9wpn5TWAbniFWwUMPuvXRJuorSYGq5r5T4QzfVbsqeYLt9xihCqaSwJjyGkskrbXgXqhWyeyR-2FeGbuoTLIBf1BYpvHpm7-2F2Ikho0ZdpSE-2F4Ur0kIbyotKYrQTLczk-2B66v-2FBt-2FX9Yn5qdF-2BlfIPn5hQeVNQlPKsqGbA4-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</p></div>
_______________________________________________<br class="">swift-corelibs-dev mailing list<br class=""><a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev<br class=""></div></blockquote></div><br class=""></body></html>