printing_unittests depends on gtestmain.lib. See src/printing/printing.gyp.
On Wed, Jun 24, 2009 at 12:46 AM, Jickae Davis<jick...@gmail.com> 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 <a...@chromium.org>
>>
>> On Mon, Jun 22, 2009 at 7:55 PM, Jickae Davis<jick...@gmail.com> 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: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
