Let me re-iterate (because even some co-workers are getting confused): I&#39;m not secretly trying to get the mac port to start using GYP.  (Or saying it&#39;s a bad idea either, mind you.)  I&#39;m just concerned that the process associated with adding a file (or adding a dependency between projects on the mac port) is out of hand--and has been for some time.  And I&#39;m hoping we can come to some sort of conclusion that&#39;ll start the project moving in the right direction--even if it&#39;s slowly.  That&#39;s it.  I promise!<div>

<br></div><div>J<br><br><div class="gmail_quote">On Thu, Aug 12, 2010 at 3:37 PM, Jeremy Orlow <span dir="ltr">&lt;<a href="mailto:jorlow@chromium.org">jorlow@chromium.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class="gmail_quote"><div class="im">On Thu, Aug 12, 2010 at 7:18 AM, David Kilzer <span dir="ltr">&lt;<a href="mailto:ddkilzer@webkit.org" target="_blank">ddkilzer@webkit.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<div>On Aug 12, 2010, at 3:54 AM, Dumitru Daniliuc &lt;<a href="mailto:dumi@chromium.org" target="_blank">dumi@chromium.org</a>&gt; wrote:<br>
<br>
&gt; i completely agree with jeremy. is it possible to at least drop the cryptic hashcodes/timestamps? without them, the .xcodeproj files should at least be editable by hand.<br>
<br>
</div>Doesn&#39;t gyp already generate Xcode projects for Chrome?  I think the issue is that gyp can&#39;t generate replacement project files for Apple&#39;s Mac port or other build systems yet.  That was my take-away from the last discussion--that gyp needed to be enhanced so that all build systems could be generated, making addition or removal of source files a trivial task.<br>


</blockquote><div><br></div></div><div>Chrome has been using GYP for some time and it&#39;s pretty stable.  I suspect that anyone trying to port the Mac port&#39;s xcode project to it will run into some bugs and/or need to build some additional features into it, but it is quite stable.  And the GYP guys are very friendly people though, so I bet they&#39;d be happy to help with any such problems.  It&#39;s also worth noting that GYP was designed from the start to allow a project to move over to it slowly (you can have custom projects depend on GYP projects and vice versa).</div>


<div><br></div><div>But moving to GYP is definitely not the only way to solve this issue--and quite possibly not the best way.  I suspect that there are also many smaller steps that could be taken that&#39;d have a big impact.  For example, coming up with ways to generate sane/informative error messages for when someone doesn&#39;t export some symbol/header file properly would awesome and doesn&#39;t require changing the entire build system.  Or creating some script that can add files to the xcode project.</div>


<div><br></div><div>J</div></div>
</blockquote></div><br></div>