It's set through .sln dependencies; src\chrome>python tools\build\win\sln_deps.py chrome.sln printing_unittests printing_unittests base gtest gtestmain icui18n icuuc printing
M-A 2009/6/25 Jickae Davis <[email protected]>: > ah...., in fact, I don't really understand what the .gyp files do. > Could the gtestmain be found in printing_unittests' project properties under > VS2005? > I have check that, and didn't find a gtestmain.lib in "Configuration > Properties"-->"Linker"-->"Input". > 2009/6/25 William Chan (陈智昌) <[email protected]> >> >> printing_unittests depends on gtestmain.lib. See >> src/printing/printing.gyp. >> >> On Wed, Jun 24, 2009 at 12:46 AM, Jickae Davis<[email protected]> wrote: >> > yep, for base_unittests, that's true. >> > But what I want to know is how chromium uses GTest. An important problem >> > is >> > how it runs all the GTest projects. >> > Take the simplest GTest project printing_unittests as an example, I know >> > it's run via GTest's main in run_all_unittests.cc. But I don't know how >> > it >> > invokes the main. I checked the project properties of >> > printing_unittests, >> > and didn't find a link to gtestmain.lib as I always do while writing >> > GTest >> > tests. >> > >> > >> > 2009/6/23 Adam Langley <[email protected]> >> >> >> >> On Mon, Jun 22, 2009 at 7:55 PM, Jickae Davis<[email protected]> wrote: >> >> > But I find something weird in the chromiun's GTest projects, they >> >> > neither >> >> > write a main nor link a gtest_main.lib. >> >> > >> >> > How do they start GTest? >> >> >> >> Well, you can always set a breakpoint at main and see where you end >> >> up. For base_unittests, it's base/run_all_unittests.cc for example. >> >> >> >> >> >> AGL >> > >> > >> > > >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
