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. 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
