Lines Matching +full:build +full:- +full:docs

35   * Does automatic verification of expectations (no record-and-replay needed).
56   * Learn the [basics](../../master/googletest/docs/primer.md) of
58   * Read [Google Mock for Dummies](../../master/googlemock/docs/ForDummies.md).
59   * Read the instructions below on how to build Google Mock.
63 Once you understand the basics, check out the rest of the docs:
65   * [CheatSheet](../../master/googlemock/docs/CheatSheet.md) - all the commonly used stuff
67   * [CookBook](../../master/googlemock/docs/CookBook.md) - recipes for getting things done,
71 [KnownIssues](docs/KnownIssues.md) and
72 [FrequentlyAskedQuestions](docs/FrequentlyAskedQuestions.md) before
82 …y C++ testing framework](../../master/googlemock/docs/ForDummies.md#using-google-mock-with-any-tes…
93     ../../master/googlemock/docs/ForDummies.md#using-google-mock-with-any-testing-framework)
101   * GNU-compatible Make or "gmake"
102   * POSIX-standard shell
103   * POSIX(-2) Regular Expressions (regex.h)
104   * C++98-standard-compliant compiler (e.g. GCC 3.4 or newer)
118 build Google Mock and its tests, which has further requirements:
124     re-generating certain source files from templates)
131 [build instructions][gtest_cmakebuild]
148 #### Preparing to Build (Unix only) ####
150 If you are using a Unix system and plan to use the GNU Autotools build
151 system to build Google Mock (described below), you'll need to
154 To prepare the Autotools build system:
157     autoreconf -fvi
159 To build Google Mock and your tests that use it, you need to tell your
160 build system where to find its headers and source files.  The exact
161 way to do it depends on which build system you use, and is usually
165 existing build system.
169 build Google Mock, create a library build target (or a project as
172     ${GTEST_DIR}/src/gtest-all.cc and ${GMOCK_DIR}/src/gmock-all.cc
182 in the normal header search path.  Assuming a Linux-like system and gcc,
185     g++ -isystem ${GTEST_DIR}/include -I${GTEST_DIR} \
186         -isystem ${GMOCK_DIR}/include -I${GMOCK_DIR} \
187         -pthread -c ${GTEST_DIR}/src/gtest-all.cc
188     g++ -isystem ${GTEST_DIR}/include -I${GTEST_DIR} \
189         -isystem ${GMOCK_DIR}/include -I${GMOCK_DIR} \
190         -pthread -c ${GMOCK_DIR}/src/gmock-all.cc
191     ar -rv libgmock.a gtest-all.o gmock-all.o
193 (We need -pthread as Google Test and Google Mock use threads.)
199     g++ -isystem ${GTEST_DIR}/include -isystem ${GMOCK_DIR}/include \
200         -pthread path/to/your_test.cc libgmock.a -o your_test
203 use to build Google Mock on systems where GNU make is available
204 (e.g. Linux, Mac OS X, and Cygwin).  It doesn't try to build Google
206 a sample test.  You can use it as a starting point for your own build
226 build the library and tests (or open the gmock.sln in the MSVC IDE).
231  * Right-click on your project and select "Add Existing Property Sheet..."
246 see file [${GTEST\_DIR}/include/gtest/internal/gtest-port.h](
247 ../googletest/include/gtest/internal/gtest-port.h).
264     -DGTEST_USE_OWN_TR1_TUPLE=0
270     -DGTEST_USE_OWN_TR1_TUPLE=1
280 Google Mock is compact, so most users can build and link it as a static
295 users' long-term benefits.  This section describes what you'll need to
302 Library](../googletest/#choosing-a-tr1-tuple-library)".
307 Google Mock use it in order to be thread-safe.  For this to work, you
309 "[Multi-threaded Tests](../googletest#multi-threaded-tests
315 [monomorphic](./docs/CookBook.md#writing-new-monomorphic-matchers),
316 [polymorphic](./docs/CookBook.md#writing-new-polymorphic-matchers)).
322 [gtest_cmakebuild]:  ../googletest/README.md#using-cmake "Using CMake"
323 [gtest_incorpcmake]: ../googletest/README.md#incorporating-into-an-existing-cmake-project "Incorpor…