On Tue, Apr 20, 2010 at 1:20 AM, Prashant <
pvsh...@gmail.com> wrote:
> Congrats Google Test Team for v1.5.
>
> Just one query for New feature: prints help when encountering
> unrecognized Google Test flags.
> What if I have added my own custom flags using google-gflags? Will
> they get recognized?
It should work if you parse the command line using google-gflags first
and call InitGoogleTest() with the remaining command line flags.
(google-gflags removes flags it recognizes from the command line.)
Thanks,
>
> Thanks,
> Prashant
>
> On Apr 17, 12:40 am, Alexander Demin <
ade...@gmail.com> wrote:
>> Great! Let's massage it a bit ;-)
>>
>> Alexander
>>
>>
>>
>> On Fri, Apr 16, 2010 at 20:33, Vlad Losev <
vl...@google.com> wrote:
>> > Dear Google Test users,
>>
>> > I'm pleased to announce the release of Google Test 1.5.0. You can download
>> > it from the project homepage athttp://
code.google.com/p/googletest/now.
>>
>> > The release contains many interesting features. They are all listed in the
>> > CHANGES<
http://code.google.com/p/googletest/source/browse/tags/release-1.5.0/...>file in the distribution package but here are the most important ones:
>>
>> > - On systems that support pthreads, you can now safely invoke test
>> > assertions from multiple threads.
>> > - Predicates used inside EXPECT_TRUE can now generate custom failure
>> > messages.
>> > - You can now build Google Test into a DLL.
>> > - Google Test now prints help when encountering flags meant for it that
>> > it can't recognize.
>> > - Experimental: CMake build script (requires CMake 2.6.4+).
>>
>> > We also made some breaking changes. Please read the following carefully to
>> > see if you are affected:
>>
>> > * Building Google Test with Visual C++ 7.1 with exceptions disabled
>> > required maintaining special code.
>> > It appears that very few people use this configuration, so we dropped
>> > support for it.
>> > Please note that you can still compile Google Test with VC++ 7.1 with
>> > exceptions enabled.
>> > * Installing Google Test libraries into system paths using make install can
>> > lead to linking with wrong libraries.
>> > This was causing quite a bit of confusion among people and generating a
>> > lot of support requests
>> > so we decided to drop support for 'make install'.
>>
>> > Many of these features are here in thanks to contributions and
>> > encouragement of our users. Thank you for them! Please enjoy the release and
>> > if you find any problems or questions about it, let us know.
>>
>> > Regards,
>> > Vlad, on behalf of the Google Test team
>>
>> --
>> Subscription settings:
http://groups.google.com/group/googletestframework/subscribe?hl=en
>
--
Zhanyong