2009/11/10 Roberto <robj.pe...@gmail.com>: > Hello, > > As you know, Chromium is a huge project, only checking out the code > and compiling it is a very costly task. > Some time ago I was browsing the Code, compiled it and also made some > changes in order to patch some bug ( the one about drag & dropping a > items in Mac version ) > > Now I want to dive again into de code, but all my compiled code is > outdated, so i need to update the code and recompile the full tree > again. > I still remember that compiling the full source code took my macbook > around 2 hr and it replaced my calefactor for a while :). > > The question is if there is any way to take only the code that you > want to work on and get the compiled libs of modules you don't want to > modify. > > Say, i want to code in V8 module but i don't want to checkout the > webkit one and spend half and hour building the library and its > dependencies, or worse, recompile again the whole module when I sync > the code to update the changes has been made.
V8 is special in that it has its own project on http://code.google.com/p/v8 and if the things you want to do don't affect the API you can do your changes on V8 without compiling Chromium. Of course Chromium still has to work when you have done your change. Running V8 tests (the normal ones, the Mozilla ones and the Sputnik ones) helps make that likely. > > I would be perfect if you could have a precompiled version of > everything and only build the module you want to solve a bug. I think > than this approach would make the entry stages more affordable. > > Thanks. > Roberto. > > -- > 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
