[webkit-dev] Towards a unified build system

Jeremy Orlow jorlow at chromium.org
Tue Mar 1 13:13:32 PST 2011

On Tue, Mar 1, 2011 at 11:08 AM, Nikolas Zimmermann <
zimmermann at physik.rwth-aachen.de> wrote:

> Am 01.03.2011 um 18:33 schrieb Maciej Stachowiak:
> >
> > On Mar 1, 2011, at 5:18 AM, Adam Roben wrote:
> >
> >> Reducing the number of build systems is a face-meltingly worthy goal. I
> have one small question:
> >>
> >> On Mar 1, 2011, at 4:21 AM, Adam Barth wrote:
> >>
> >>> 3) Remove the xcodeproj files from svn.webkit.org and integrate the
> >>> generation of xcodeproj files with the WebKit build / update scripts.
> >>> At this point, contributors will notice that something has changed
> >>> because there'll be one less build system to worry about keeping up to
> >>> date!
> >>
> >> Won't contributors who don't use update-webkit/build-webkit also notice
> something has changed, because they will no longer have any project files?
> (I ask this as a contributor who doesn't use update-webkit/build-webkit.)
> >
> > Another consequence of step 3 is it would break submissions to Apple's
> central build system, since those pull from the repository with vanilla SVN
> and do not run special scripts afterwards.
> What about checking in the generated Xcodeproj? Would that be an option?

We could quickly find ourselves in the position of generating build files
for many different ports every time we submit patches, which could add
several minutes to the submit process (which is even worse if you lose a
race with another committer and have to update/rebase and try again).
 Generating on checkout seems like the best answer--if feasible.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20110301/d69c8b5a/attachment.html>

More information about the webkit-dev mailing list