<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="">The comment in question referenced:<div class=""><br class=""></div><div class=""><a href="https://developer.apple.com/documentation/xcode_release_notes/xcode_10_release_notes/build_system_release_notes_for_xcode_10" class="">https://developer.apple.com/documentation/xcode_release_notes/xcode_10_release_notes/build_system_release_notes_for_xcode_10</a></div><div class=""><br class=""></div><div class="">I'd commend that to anyone involved, because even though I don't really understand build systems that go too much beyond makefiles, possibly preprocessed to get around the limitations of many versions of make, let alone nontrivial IDE's such as Xcode, it's quite obvious that a number of the bullet points in that article, esp. in the "Overview" section, are quite likely to relate to some of the problems with the new build system, such as files not being there when expected, or not being found, and probably other issues too.</div><div class=""><br class=""></div><div class="">While the breakage is certainly a PITA, that some things need to be changed to be more explicit is probably good in the long run, insofar as one has to be using a proprietary build system at all rather than relatively generic command line stuff (IMO); once the current breakage is fixed, one might hope the result would be more robust in the future. At least that's my impression of what's _supposed_ to happen. :-)</div><div class=""><br class=""></div></body></html>