<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Dave,<div class=""><br class=""></div><div class="">Let me talk to a few people offline and get back to you on this. We should be able to get it setup correctly.</div><div class=""><br class=""></div><div class="">- Tony</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 12, 2016, at 7:56 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="">Hi,<br class=""><br class=""> After libdispatch PR#49 gets merged, it would be feasible to start including libdispatch in the linux buildbot presets and thus (I think) in the development snapshots as well.<br class=""><br class=""> The additional libdispatch pre-reqs (libblocksruntime-dev libkqueue-dev systemtap-sdt-dev autoconf libtool) would need to be installed on the build machines.<br class=""><br class=""> Because libpwq is being included as a gitsubmodule, there are extra steps after cloning swift-corelibs-libdispatch (git submodule init; git submodule update) that the automated build would need to do.<br class=""><br class=""> Is there anything I can do to help move this along? Anything I've overlooked?<br class=""><br class="">thanks,<br class=""><br class="">--dave<br class=""><br 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=""></div></body></html>