<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="">Hello mailing-list,<div class=""><br class=""></div><div class="">I’m implementing <a href="https://bugs.swift.org/browse/SR-3583" class="">SR-3583</a> that builds SwiftPM products into platform-specific sub-folders. For example, on macOS, a default build will no longer build products into <b class="">.build/debug</b> but instead in <b class="">.build/macosx-x86_64/debug</b>.</div><div class=""><br class=""></div><div class="">To alleviate this breaking change, several solutions have been planned:</div><div class=""><br class=""></div><div class=""><ul class="MailOutline"><li class=""><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0179-swift-run-command.md" class="">SE-0179</a>: A new <b class="">swift run</b> tool to allow users to run executable products without knowing their exact location.</li><li class="">SR-3583 will create a symlink after each build pointing from the old to the new build folder for backwards compatibility.</li><li class=""><a href="https://bugs.swift.org/browse/SR-5259" class="">SR-5259</a>: A new <b class="">—bin-path</b> option for the <b class="">swift build</b> command to print the build folder for 3rd party tools to use.</li></ul><div class=""><br class=""></div></div><div class="">Of the above, only SE-0179 is currently fully implemented in master.</div><div class=""><br class=""></div><div class="">What does everybody think about this change and the solutions put into place to support it?</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">David.</div></body></html>