Continuing with this issue, I'm not sure if this is possible, but the builbots can copy the library builds to a revision based directory structure before the final executable is built. For example, the buildbot which compile webkit module, and copy the webkit library to that directory.
So, when you use gclient to sync the repository, you will be able to download the already built libraries (by the builbots) corresponding to the revision you're syncing. With this, a full initial checkout will produce a structure where you only need to rebuild the modules you've changed their sourcecode to get the final executable. On Tue, Nov 10, 2009 at 11:34 PM, Jeremy Orlow <jor...@chromium.org> wrote: > On Tue, Nov 10, 2009 at 2:31 PM, Roberto Perez <robj.pe...@gmail.com>wrote: > >> As Phistuck said, modifying gclient config file and then skipping the >> changes of the modules that you're not working on seems a good solution to >> prevent continuous rebuildings of other modules. >> >> But this doesn't skip the first large build. >> >> I know that download already built modules isn't the best option but, for >> example, you could download the libs that buildbot builds (before linking in >> a single executable) and with these modules already built, satisfy the >> requeriments to build a single module on your own. >> >> I'm not talking about splitting the modules into different projects, but >> speed up the first stages of working in some module. >> > > It seems like that might be useful to some people. Maybe you could > prototype such a tool? > > >> On Tue, Nov 10, 2009 at 9:30 PM, Marc-Antoine Ruel <mar...@google.com>wrote: >> >>> And you can use distcc. >>> >>> >>> On Tue, Nov 10, 2009 at 1:21 PM, Paweł Hajdan jr <phajdan...@gmail.com> >>> wrote: >>> > Note however that you can build specific projects. When working on base >>> or >>> > net for example, you can build just base_unittests and net_unittests. >>> When >>> > working on webkity things, you can sometimes compile just the >>> test_shell, >>> > and not chrome. >>> > >>> > -- >>> > Chromium Developers mailing list: chromium-dev@googlegroups.com >>> > View archives, change email options, or unsubscribe: >>> > http://groups.google.com/group/chromium-dev >>> >> >> -- >> Chromium Developers mailing list: chromium-dev@googlegroups.com >> View archives, change email options, or unsubscribe: >> http://groups.google.com/group/chromium-dev >> > > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
