FYI, I fixed a dependency bug in chrome.gyp earlier in the week, so there's a much greater chance of make finishing on the first try. I have several gyp fixes floating around, and I'll try to set up a make buildbot today/early next week.
On Tue, Aug 18, 2009 at 5:44 AM, Evan Martin<e...@chromium.org> wrote: > I would like to make this switch, but it is not yet reliable. I don't > want build bots failing because of dependency bugs. (Heh, heaven > forbid we sometimes need to click a hypothetical "clobber" checkbox on > the buildbots to work around a build system issue! :P) > > I'd been using the "makebuild" label, though most bugs have just been > reported to me directly (special thanks to benl and davemoore for > tracking down some problems for me): > http://code.google.com/p/chromium/issues/list?can=1&q=makebuild > > Dean told me he has his build alias just always run make twice when he > builds, which is pretty tragic to me, but he says it's still faster > than scons. :\ > > > On Mon, Aug 17, 2009 at 2:07 PM, Lei Zhang<thes...@chromium.org> wrote: >> >> Hi, >> >> On Linux, building with make is a lot faster than build with hammer. >> Ever since I switched to the make build on Linux, I've never looked >> back. I imagine many other Linux developers are also using make, and >> we have been using the make build without any major problems for a few >> months now. So I wonder, is it time to switch our build bots to make >> and update the Linux build instructions? >> >> - Lei >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
