On Saturday, 20 February 2016, Max Howell <<a href="mailto:max.howell@apple.com">max.howell@apple.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> In that context, I have a few questions:<br>
> * Is it intended that the generated Xcode project will be checked-in?<br>
<br>
It’s up to you, but certainly it will not be required and we will recommend NOT editing the generated project.<br>
<br>
> * Will the project duplicate information that SwiftPM specifies? file references? configuration?<br>
<br>
Yes, because it will be generated, consider it a build artefact.<br>
<br>
> * Will the rebuild clobber project configuration that SwiftPM can't specify? This is probably fine. Maybe Xcode should make configuration read-only in generated projects.<br>
<br>
Yes… don’t edit the projects! ;)</blockquote><div><br></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)">Thanks, that's what I expected, and is what I was hoping for.</span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div><span style="background-color:rgba(255,255,255,0);font-size:small">My main point then is that I expect users won't</span><span style="background-color:rgba(255,255,255,0);font-size:small"> realise their changes will be clobbered. It would be good if </span><span style="background-color:rgba(255,255,255,0);font-size:small">Xcode's configuration</span><span style="background-color:rgba(255,255,255,0);font-size:small"> UI is</span><span style="background-color:rgba(255,255,255,0);font-size:small"> read-only for these projects. At least for v1, if the engineering cost is sufficiently low.</span><br></div><div><br></div>