To make things clear: my only intention for trying to build this port was due to my patch failed to compile in it. I'm not advocating towards using it for regular development. Perhaps, I would get the same compile issue when building Chromium on Windows, but, as I usually avoid using Windows, and haven't had a ready-to-use configuration at that moment, I decided to try to build the port, to make sure that this isn't a bot issue.
Dimitri, I'm currently following building the port using your instructions for setting up a build bot, and it almost works, thank you very much! I'll update docs later, after I'll finish with it. On Thu, Aug 25, 2011 at 18:31, Dimitri Glazkov <[email protected]> wrote: > On Thu, Aug 25, 2011 at 10:21 AM, Peter Kasting <[email protected]> wrote: >> On Thu, Aug 25, 2011 at 10:07 AM, Mikhail Naganov <[email protected]> >> wrote: >>> >>> I'm not sure we are on the same page. I'm talking about Chromium port >>> of WebKit, where Chromium checkout is _inside_ WebKit's >>> Source/WebKit/chromium, as opposed to when you have full WebKit >>> checkout inside Chromium's third_party. >> >> Yes, we're saying always use the latter, as it lets you test the same things >> and it's much more well-supported and tested :) > > FWIW, I use the former exclusively on Mac. I don't see a need for a > typical WebKit developer who lives in WebCore to ever carry a Chromium > checkout. > > :DG< > > >> PK >> _______________________________________________ >> webkit-dev mailing list >> [email protected] >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >> >> > _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
