<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 12, 2017, at 6:06 PM, Saleem Abdulrasool via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><br class=""></div><div class="">The problems with the cross-compiling that Im referring to are not inherent to CMake (although, I am slightly partial to the autotools approach to cross-compilation), but rather the way that the tool is being used within the context of swift. As an example, libdispatch is extremely easy to cross-compile thanks to its use of CMake.</div></div></div></div></div></blockquote><br class=""></div><div>CMake's cross-compilation machinery was unable to build for iOS at the time that Swift needed it. It's possible that CMake has improved enough since then that Swift could use more of CMake's built-in capabilities.</div><div><br class=""></div><div><br class=""></div><div>-- </div><div>Greg Parker <a href="mailto:gparker@apple.com" class="">gparker@apple.com</a> Runtime Wrangler</div><div><br class=""></div><br class=""></body></html>