It's not that simple. I think something fishy is going on with our project dependencies or something.
I just setup a new machine last week and when I have Chrome as my startup project and press F5 it builds no less than 18 (!) projects. Most of which look like tests. Just look at the list below (detailed steps after first two projects omitted for clarity). 1>------ Build started: Project: crash_service, Configuration: Debug Win32 ------ 1>Linking... 1>Embedding manifest... 1>Build log was saved at "file://E:\code\src\chrome\Debug\obj\crash_service\BuildLog.htm" 1>crash_service - 0 error(s), 0 warning(s) 2>------ Build started: Project: chrome_exe, Configuration: Debug Win32 ------ 2>Linking... 2>Embedding manifest... 2>.\chrome.exe.manifest : manifest authoring warning 81010002: Unrecognized Element "requestedPrivileges" in namespace "urn:schemas-microsoft-com:asm.v3". 2>Copy first run complete sentinel file 2> 1 file(s) copied. 2>Build log was saved at "file://E:\code\src\chrome\Debug\obj\chrome_exe\BuildLog.htm" 2>chrome_exe - 0 error(s), 1 warning(s) 3>------ Build started: Project: setup, Configuration: Debug Win32 ------ 4>------ Build started: Project: generate_profile, Configuration: Debug Win32 ------ 5>------ Build started: Project: perf_tests, Configuration: Debug Win32 ------ 6>------ Build started: Project: ui_tests, Configuration: Debug Win32 ------ 7>------ Build started: Project: startup_tests, Configuration: Debug Win32 ------ 8>------ Build started: Project: selenium_tests, Configuration: Debug Win32 ------ 9>------ Build started: Project: reliability_tests, Configuration: Debug Win32 ------ 10>------ Build started: Project: page_cycler_tests, Configuration: Debug Win32 ------ 11>------ Build started: Project: unit_tests, Configuration: Debug Win32 ------ 12>------ Build started: Project: stats_viewer, Configuration: Debug Any CPU ------ 13>------ Build started: Project: tab_switching_test, Configuration: Debug Win32 ------ 14>------ Build started: Project: memory_test, Configuration: Debug Win32 ------ 15>------ Build started: Project: plugin_tests, Configuration: Debug Win32 ------ 16>------ Build started: Project: interactive_ui_tests, Configuration: Debug Win32 ------ 17>------ Skipped Build: Project: mini_installer, Configuration: Debug Win32 ------ 17>Project not selected to build for this solution configuration 18>------ Build started: Project: installer_unittests, Configuration: Debug Win32 ------ 19>------ Build started: Project: automated_ui_tests, Configuration: Debug Win32 ------ ========== Build: 18 succeeded, 0 failed, 146 up-to-date, 1 skipped ========== On Tue, Mar 31, 2009 at 12:39, Adam Barth <[email protected]> wrote: > > This isn't how Visual Studio 2005 works for me. Are you sure that the > chrome_exe project is your startup project (i.e., it's bold in the > tree view on the left) and you're pressing F5 (and not F7 or > Shift-F7)? > > Adam > > > On Tue, Mar 31, 2009 at 12:34 PM, QAH <[email protected]> wrote: > > > > When I do that, it still reaches into the "unit_tests" subproject and > > tries to compile that code. I don't want it to do that because it > > gives me lots of errors from the unit tests. > > > > On Mar 31, 3:30 pm, Adam Barth <[email protected]> wrote: > >> Set chrome_exe as your startup project and press F5! > >> > >> Adam > >> > >> > >> > >> On Tue, Mar 31, 2009 at 12:14 PM, QAH <[email protected]> wrote: > >> > >> > Hello everyone! I got google chrome to compile, but there were lots of > >> > errors given to me with the unit tests. The browser can still run > >> > without the tests, so how can I stop the unit tests from being > >> > compiled and just compile and run the browser itself? > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
