[webkit-dev] Build File Maintenance (was Re: Please welcome GYP to the our dysfunctional build family)
jorlow at chromium.org
Fri Jul 10 18:54:17 PDT 2009
On Fri, Jul 10, 2009 at 6:26 PM, Kevin Ollivier <kevino at theolliviers.com>wrote:
> Hi Jeremy,
> On Jul 10, 2009, at 3:03 PM, Jeremy Orlow wrote:
> Your argument makes sense if WebKit is only built for one
> platform/build-system. Unfortunately it's not. So the question is whether
> it's easier to maintain lots of different build files or whether it's easier
> to maintain one file that's perhaps a bit more abstract + the tool that
> interprets it.
> I agree that working directly in the project file for your platform is
> easier IF you're only developing for one platform. But once you start
> maintaining more than one project file, I think GYP is a big win.
> While we hope that others will update our GYPI file when they add/remove
> files, our build depends on it...so we'll definitely be keeping it in sync.
> So I think the question then becomes whether it's easier for you to
> maintain your new build format, or whether it's easier to make it a target
> GYP. I honestly don't know what the answer is, but I think it's worth taking a closer look at GYP.
> Actually, the big question in regards to having GYP reduce overall project
> maintenance is whether or not the other ports will adopt GYP. If the answer
> is yes, then it would be more compelling for wx to do so as well, assuming
> of course that someone implements a waf backend so that we can. :-) If the
> answer is no, though, then GYP is not reducing the amount of project
> maintenance work for any port other than Chromium, in which case there will
> still be 6 build systems (still 5 even if wx were to switch) and the problem
> I originally posed in this thread will still be an issue. In that case, the
> only way to really reduce the maintenance work of adding / removing files
> would again be to adopt a script like the one I suggested earlier.
You're right. The burden of updating the GYPI file is less than the others,
but it's still another file you need to change. But note that the
maintainers of each project/platform/etc define which files to exclude.
This is different from the other build systems where the person updating
the file needs to decide whether it should go into the build or whether it
should only be built with certain flags.
> Speaking of which, with waf / Python I've actually almost completely
> automated the generation of the list of include dirs for my build projects
> based on the source files, so that I'm not maintaining them by hand anymore
> except for a few exceptions. And thinking about it, I bet I can even mostly
> automate the list of source files too, by having it grab all the .cpp files
> in the common dirs and special subdirs like curl and wx, then having some
> include / exclude filters to deal with a few special cases. :-) The question
> will be the performance hit, but at least with the includes it's not even
> noticeable, and I could always look into caching and changing only when you
> do an svn up or svn add/remove.
I suggest you take a look at GYP. Much of what you're talking about it
That's the sort of flexibility and ability to quickly experiment and
> automate that scripts offer, and I suspect I will really miss that if I
> switch back to something like Bakefile / GYP.
Of course you're going to be able to experiment easier with something you
wrote yourself. That said, the generator for scons is only 780 lines of
code including a couple hundred of templates...so it doesn't seem like it'd
be _that_ hard to figure it out.
I'm not necessarily saying you guys should be using GYP, but I really think
you should take a closer look at it.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev