Lines Matching refs:to
24 Google Test is designed to have fairly minimal requirements to build
27 effort to support other platforms (e.g. Solaris, AIX, and z/OS).
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
56 Also, you'll need CMake 2.6.4 or higher if you want to build the
62 We welcome patches. If you plan to contribute a patch, you need to
84 formats are provided, but the only difference is the tools used to
109 To build Google Test and your tests that use it, you need to tell your
110 build system where to find its headers and source files. The exact
111 way to do it depends on which build system you use, and is usually
118 and Xcode) to compile
136 g++ -I${GTEST_DIR}/include path/to/your_test.cc libgtest.a -o your_test
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
152 If you see errors, try to tweak the contents of make/Makefile to make
153 them go away. There are instructions in make/Makefile on how to do
167 mkdir mybuild # Create a directory to hold the build output.
171 If you want to build Google Test's samples, you should replace the
177 current directory. Just type 'make' to build gtest.
189 continue to provide them for convenience, they are not actively
191 instructions in the previous two sections to integrate Google Test
194 If you still need to use the legacy build scripts, here's how:
198 are ready to build Google Test the same way you build any Visual
203 the same option to compile both gtest and the test code. If you use
210 "Preferences..." -> "Building" pane and defaults to xcode/build).
227 these macros are named like GTEST_XYZ and you define them to either 1
228 or 0 to enable or disable a certain feature.
241 Usually you don't need to care about which tuple library Google Test
242 uses. However, if your project already uses TR1 tuple, you need to
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
254 to the compiler flags instead.
256 If you don't want Google Test to use tuple at all, add
266 macro to see whether this is the case (yes if the macro is #defined to
278 When Google Test uses pthread, you may need to add flags to your
279 compiler and/or linker to select the pthread library, or you'll get
282 script, you'll need to read your compiler and linker's manual to
283 figure out what flags to add.
288 static library for the simplicity. You can choose to use Google Test
295 to the compiler flags. You'll also need to tell the linker to produce
296 a shared library instead - consult your linker's manual for how to do
303 to the compiler flags.
307 future, if we decide to improve the speed of loading the library (see
309 recommended to always add the above flags when using Google Test as a
318 library, you can force Google Test to rename its macro to avoid the
326 to the compiler flags to tell Google Test to change the macro's name
327 from FOO to GTEST_FOO. Currently FOO can be FAIL, SUCCEED, or TEST.
328 For example, with -DGTEST_DONT_DEFINE_TEST=1, you'll need to write
336 in order to define a test.
341 We strive to keep Google Test releases backward compatible.
342 Sometimes, though, we have to make some breaking changes for the
343 users' long-term benefits. This section describes what you'll need to
348 You may need to explicitly enable or disable Google Test's own TR1
355 supportted. You are encouraged to migrate to your own build system or
356 use CMake. If you still need to use Autotools, you can find
360 it in order to be thread-safe. See the "Multi-threaded Tests" section
361 for what this means to your build script.
366 anyway. We decided to stop supporting it in order to greatly simplify
372 This section discusses how to make your own changes to Google Test.
377 functionality, you'll want to compile and run Google Test's own tests.
386 able to find Python ("Could NOT find PythonInterp (missing:
390 cmake -DPYTHON_EXECUTABLE=path/to/python -Dgtest_build_tests=ON ${GTEST_DIR}
404 file include/gtest/internal/gtest-type-util.h.pump is used to generate
407 Normally you don't need to worry about regenerating the source files,
408 unless you need to modify them. In that case, you should modify the
409 corresponding .pump files instead and run the pump.py Python script to
411 Read the Pump manual [2] for how to use it.
419 the Contributor License Agreement, or we won't be able to accept the