Lines Matching refs:Google

1 Google C++ Testing Framework
9 Google's framework for writing C++ tests on a variety of platforms
24 Google Test is designed to have fairly minimal requirements to build
28 However, since core members of the Google Test project have no access
29 to these platforms, Google Test may have outstanding issues there.  If
36 These are the base requirements to build and use Google Test from a source
63 build Google Test and its own tests from an SVN checkout (described
73 There are two primary ways of getting Google Test's source code: you
82 Google Test is released in versioned source packages which can be
101 To check out the main branch (also known as the "trunk") of Google
109 To build Google Test and your tests that use it, you need to tell your
116 Suppose you put Google Test in directory ${GTEST_DIR}.  To build it,
139 use to build Google Test on systems where GNU make is available
140 (e.g. Linux, Mac OS X, and Cygwin).  It doesn't try to build Google
141 Test's own tests.  Instead, it just builds the Google Test library and
158 Google Test comes with a CMake build script (CMakeLists.txt) that can
171 If you want to build Google Test's samples, you should replace the
191 instructions in the previous two sections to integrate Google Test
198 are ready to build Google Test the same way you build any Visual
220 Tweaking Google Test
223 Google Test can be used in diverse environments.  The default
225 some environments.  However, you can easily tweak Google Test by
235 Some Google Test features require the C++ Technical Report 1 (TR1)
237 good news is that Google Test implements a subset of TR1 tuple that's
241 Usually you don't need to care about which tuple library Google Test
243 tell Google Test to use the same TR1 tuple library the rest of your
249 to the compiler flags while compiling Google Test and your tests.  If
250 you want to force Google Test to use its own tuple library, just add
256 If you don't want Google Test to use tuple at all, add
264 Google Test is thread-safe where the pthread library is available.
269 If Google Test doesn't correctly detect whether pthread is available
278 When Google Test uses pthread, you may need to add flags to your
287 Google Test is compact, so most users can build and link it as a
288 static library for the simplicity.  You can choose to use Google Test
309 definitions.  In case a Google Test macro clashes with another
310 library, you can force Google Test to rename its macro to avoid the
313 Specifically, if both Google Test and some other code define macro
318 to the compiler flags to tell Google Test to change the macro's name
333 We strive to keep Google Test releases backward compatible.
336 do if you are upgrading from an earlier version of Google Test.
340 You may need to explicitly enable or disable Google Test's own TR1
349 instructions in the README file from Google Test 1.4.0.
351 On platforms where the pthread library is available, Google Test uses
355 If you use Microsoft Visual C++ 7.1 with exceptions disabled, Google
359 Google Test's implementation.
361 Developing Google Test
364 This section discusses how to make your own changes to Google Test.
366 ### Testing Google Test Itself ###
369 functionality, you'll want to compile and run Google Test's own tests.
376 Make sure you have Python installed, as some of Google Test's tests
385 Next, you can build Google Test and all of its own tests.  On *nix,
394 Some of Google Test's source files are generated from templates (not
410 We welcome patches.  Please read the Google Test developer's guide [3]