No subject


Wed Aug 1 07:28:53 PDT 2012


One minor nit, but I'll reply with that on the bug. Thanks for doing this!

Peter

On Mon, Dec 10, 2012 at 9:39 AM, Eric Seidel <eric at webkit.org> wrote:

> The buildbots will use ninja by default, but could opt-out (with
> --no-ninja) if that were desired behavior.
>
>
> I've so far received one other concern:
> Robert Hogan raised that chromium's depot_tools does not contain a
> 32-bit build of ninja, and the error message is somewhat confusing in
> that case.  I've filed https://bugs.webkit.org/show_bug.cgi?id=104523
> for tracking that issue.
>
> On Mon, Dec 10, 2012 at 1:30 AM, Jochen Eisinger <jochen at chromium.org>
> wrote:
> > Will the buildbots use ninja or the "native" build tools?
> >
> > My only concern is that we're catching problems with e.g. MSVS only
> after we
> > roll the WebKit deps in chromium and one of the MSVS bots starts failing.
> >
> > Otherwise, I'm all for switching to ninja.
> >
> > best
> > -jochen
> >
> > On Sat, Dec 8, 2012 at 9:29 AM, Eric Seidel <eric at webkit.org> wrote:
> >>
> >> If you don't work on the Chromium port, feel free to ignore.
> >>
> >>
> >> If you work on the Chromium port of WebKit and do not use Ninja as you
> >> build system (GYP_GENERATORS='ninja' or update-webkit --chromium
> >> --ninja) I want to hear from you!
> >>
> >> As far as I can tell, the vast majority of Chromium contributors use
> >> Ninja as their build system of choice.  Particularly for
> >> Chromium-Android contributors this seems to be true.
> >>
> >> With that knowledge, I have posted a patch to make update-webkit
> >> ---chromium/--chromium-android generate Ninja build files instead of
> >> platform-native build files (XCode, Visual Studio, Make, etc.) by
> >> default.  This of course only affects the chromium port.
> >>
> >> https://bugs.webkit.org/show_bug.cgi?id=104434
> >>
> >> Thanks!
> >>
> >>
> >> p.s. If you don't already know:
> >> update-webkit --chromium --ninja
> >> build-webkit --chromium
> >> is all you need to use Ninja today.  You don't even need to have
> >> installed/built your own copy of ninja (Chromium has done that for
> >> you).
> >>
> >> p.p.s. Ninja is awesome. Awesomely quiet. Awesomely fast.
> >> http://martine.github.com/ninja/
> >> _______________________________________________
> >> webkit-dev mailing list
> >> webkit-dev at lists.webkit.org
> >> http://lists.webkit.org/mailman/listinfo/webkit-dev
> >
> >
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo/webkit-dev
>

--001517447ceed92b4804d07e6de4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Clarifying the error messages seems like a win in either case.<div><br></di=
v><div>From Android&#39;s perspective, I&#39;m of course in favor of switch=
ing to ninja. One minor nit, but I&#39;ll reply with that on the bug. Thank=
s for doing this!<br>
<div class=3D"gmail_extra"><br>Peter<br><br><div class=3D"gmail_quote">On M=
on, Dec 10, 2012 at 9:39 AM, Eric Seidel <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:eric at webkit.org" target=3D"_blank">eric at webkit.org</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The buildbots will use ninja by default, but=
 could opt-out (with<br>
--no-ninja) if that were desired behavior.<br>
<br>
<br>
I&#39;ve so far received one other concern:<br>
Robert Hogan raised that chromium&#39;s depot_tools does not contain a<br>
32-bit build of ninja, and the error message is somewhat confusing in<br>
that case. =A0I&#39;ve filed <a href=3D"https://bugs.webkit.org/show_bug.cg=
i?id=3D104523" target=3D"_blank">https://bugs.webkit.org/show_bug.cgi?id=3D=
104523</a><br>
for tracking that issue.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Mon, Dec 10, 2012 at 1:30 AM, Jochen Eisinger &lt;<a href=3D"mailto:joch=
en at chromium.org">jochen at chromium.org</a>&gt; wrote:<br>
&gt; Will the buildbots use ninja or the &quot;native&quot; build tools?<br=
>
&gt;<br>
&gt; My only concern is that we&#39;re catching problems with e.g. MSVS onl=
y after we<br>
&gt; roll the WebKit deps in chromium and one of the MSVS bots starts faili=
ng.<br>
&gt;<br>
&gt; Otherwise, I&#39;m all for switching to ninja.<br>
&gt;<br>
&gt; best<br>
&gt; -jochen<br>
&gt;<br>
&gt; On Sat, Dec 8, 2012 at 9:29 AM, Eric Seidel &lt;<a href=3D"mailto:eric=
@webkit.org">eric at webkit.org</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; If you don&#39;t work on the Chromium port, feel free to ignore.<b=
r>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; If you work on the Chromium port of WebKit and do not use Ninja as=
 you<br>
&gt;&gt; build system (GYP_GENERATORS=3D&#39;ninja&#39; or update-webkit --=
chromium<br>
&gt;&gt; --ninja) I want to hear from you!<br>
&gt;&gt;<br>
&gt;&gt; As far as I can tell, the vast majority of Chromium contributors u=
se<br>
&gt;&gt; Ninja as their build system of choice. =A0Particularly for<br>
&gt;&gt; Chromium-Android contributors this seems to be true.<br>
&gt;&gt;<br>
&gt;&gt; With that knowledge, I have posted a patch to make update-webkit<b=
r>
&gt;&gt; ---chromium/--chromium-android generate Ninja build files instead =
of<br>
&gt;&gt; platform-native build files (XCode, Visual Studio, Make, etc.) by<=
br>
&gt;&gt; default. =A0This of course only affects the chromium port.<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://bugs.webkit.org/show_bug.cgi?id=3D104434" targe=
t=3D"_blank">https://bugs.webkit.org/show_bug.cgi?id=3D104434</a><br>
&gt;&gt;<br>
&gt;&gt; Thanks!<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; p.s. If you don&#39;t already know:<br>
&gt;&gt; update-webkit --chromium --ninja<br>
&gt;&gt; build-webkit --chromium<br>
&gt;&gt; is all you need to use Ninja today. =A0You don&#39;t even need to =
have<br>
&gt;&gt; installed/built your own copy of ninja (Chromium has done that for=
<br>
&gt;&gt; you).<br>
&gt;&gt;<br>
&gt;&gt; p.p.s. Ninja is awesome. Awesomely quiet. Awesomely fast.<br>
&gt;&gt; <a href=3D"http://martine.github.com/ninja/" target=3D"_blank">htt=
p://martine.github.com/ninja/</a><br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; webkit-dev mailing list<br>
&gt;&gt; <a href=3D"mailto:webkit-dev at lists.webkit.org">webkit-dev at lists.we=
bkit.org</a><br>
&gt;&gt; <a href=3D"http://lists.webkit.org/mailman/listinfo/webkit-dev" ta=
rget=3D"_blank">http://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
webkit-dev mailing list<br>
<a href=3D"mailto:webkit-dev at lists.webkit.org">webkit-dev at lists.webkit.org<=
/a><br>
<a href=3D"http://lists.webkit.org/mailman/listinfo/webkit-dev" target=3D"_=
blank">http://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
</div></div></blockquote></div><br></div></div>

--001517447ceed92b4804d07e6de4--


More information about the webkit-dev mailing list