I had a similar problem on VS 2005, maybe it is the same as yours. Turned out VS was set to build everything as opposed to just building what the project depended on. Not sure how to do it in VS2008, but in VS 2005, under Tools \ Options, go to: Projects and Solutions \ Build and Run Make sure "Only build startup projects and dependencies on Run" is checked.
Then (if you make sure chrome is set as the startup project) it should not be building all those tests. Hope that helps. Finnur On Fri, Jul 3, 2009 at 09:32, Mohamed Mansour <[email protected]> wrote: > It depends on the machine you have. CPU power. HD etc. ... If you have > incremental build turned on /MP it will take less time to compile as well. > -- Mohamed Mansour > > > > On Fri, Jul 3, 2009 at 12:26 PM, PhistucK <[email protected]> wrote: > >> At least in Visual Studio 2005, you can right click on the solution and in >> "Configuration Options" (or something like that), you can select what to >> build and what not to build.It does speed up the compiling process by at >> least half (for me). It still, generally, takes a lot of time. >> >> ☆PhistucK >> >> >> >> On Fri, Jul 3, 2009 at 19:21, Thiago Farina <[email protected]>wrote: >> >>> >>> Anyone knows how to speed up the process of debugging chromium in >>> Visual Studio 2008? >>> >>> Everytime I click in F5 to start debugging chromium it takes a long >>> time to compile and build project test with him. >>> >>> How can I avoid the project tests like ipc_tests, >>> interactive_ui_tests, perf_tests, etc, are compiled with chrome(exe) >>> project? >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
