[webkit-dev] Build File Maintenance (was Re: Please welcome GYP to the our dysfunctional build family)
atwilson at google.com
Fri Jul 10 11:43:29 PDT 2009
Having used both Chromium's .gyp solution and WebKit's
.<update-a-bunch-of-random-files> solution, I'd like to add a huge +1 to
anyone interested in doing this for their own port. Especially since the
lack of trybots for webkit means that it's prohibitively difficult for
people to actually test their build changes cross-platform currently.
Although maybe I'm just extra-sensitive to this since dimich and I spent a
chunk of time last night diagnosing and fixing some gtk test bustage due to
missing files from the build config.
On Fri, Jul 10, 2009 at 11:37 AM, Dimitri Glazkov <dglazkov at chromium.org>wrote:
> To add to this, GYP also only generates files for _your_ platform on
> checkout. Even to the degree that on Windows, it would generate VS2008
> projects if you had it installed, and VS2005 otherwise. To be precise,
> the selection is not automatic (you need an env variable) to avoid
> dual-VS installs ambiguity.
> On Fri, Jul 10, 2009 at 11:32 AM, Mike Pinkerton<pinkerton at chromium.org>
> > On Fri, Jul 10, 2009 at 2:20 PM, Dimitri Glazkov<dglazkov at chromium.org>
> >>> If you hand-edit Xcode project files enough times you start to
> understand them, but you also may go insane in the process. I don't know
> that you have to write a full parser for it, but there is some non-trivial,
> minimal structure you have to understand to update the file properly.
> >> GYP generates very nice XCode projects -- they are always properly
> >> sorted, logically structured, and clean.
> > I think the difference worth highlighting here is that GYP doesn't
> > *edit* Xcode projects. That is explicitly a non-goal. It generates new
> > ones from scatch every time (but is smart enough not to touch anything
> > if nothing would change). As a result, it doesn't need to know about
> > all the various ways a project file could change from state A to state
> > B.
> > In Chromium, we don't have any Xcode files checked in, they're
> > generated (again, from scratch, replacing whatever was there before)
> > on every checkout. If you want to make local changes during the course
> > of your development, that's fine (and helpful to test small tweaks),
> > but the only canonical representation of the Xcode project file is in
> > GYP.
> > --
> > Mike Pinkerton
> > Mac Weenie
> > pinkerton at google.com
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev