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

3 …build-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https://g…
6 …st-bindings](https://github.com/google/benchmark/workflows/test-bindings/badge.svg)](https://githu…
33 [User Guide](docs/user_guide.md) for a more comprehensive feature overview.
35 …read the [Google Test documentation](https://github.com/google/googletest/blob/main/docs/primer.md)
40 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss)
45 [Additional Tooling Documentation](docs/tools.md)
47 [Assembly Testing Documentation](docs/AssemblyTests.md)
49 [Building and installing Python bindings](docs/python_bindings.md)
53 The library can be used with C++03. However, it requires C++11 to build,
56 The following minimum versions are required to build the library:
63 See [Platform-Specific Build Instructions](docs/platform_specific_build_instructions.md).
67 This describes the installation process using cmake. As pre-requisites, you'll
70 _See [dependencies.md](docs/dependencies.md) for more details regarding supported
71 versions of build tools._
78 # Make a build directory to place the build output.
79 $ cmake -E make_directory "build"
80 # Generate build system files with cmake, and download any dependencies.
81 $ cmake -E chdir "build" cmake -DBENCHMARK_DOWNLOAD_DEPENDENCIES=on -DCMAKE_BUILD_TYPE=Release ../
83 # cmake -DCMAKE_BUILD_TYPE=Release -S . -B "build"
84 # Build the library.
85 $ cmake --build "build" --config Release
88 On a unix system, the build directory should now look something like this:
92   /build
100 Next, you can run the tests to check the build.
103 $ cmake -E chdir "build" ctest --build-config Release
109 sudo cmake --build "build" --config Release --target install
112 Note that Google Benchmark requires Google Test to build and run the tests. This
116 * Otherwise, if `-DBENCHMARK_DOWNLOAD_DEPENDENCIES=ON` is specified during
117   configuration as above, the library will automatically download and build
120 If you do not wish to build and run the tests, add `-DBENCHMARK_ENABLE_GTEST_TESTS=OFF`
126 output when this is the case. To build it as a release library instead, add
127 `-DCMAKE_BUILD_TYPE=Release` when generating the build system files, as shown
128 above. The use of `--config Release` in build commands is needed to properly
129 support multi-configuration tools (like Visual Studio for example) and can be
130 skipped for other build systems (like Makefile).
132 To enable link-time optimisation, also add `-DBENCHMARK_ENABLE_LTO=true` when
133 generating the build system files.
143 …-DCMAKE_C_FLAGS="-g -O2 -fno-omit-frame-pointer -fsanitize=address -fsanitize=thread -fno-sanitize…
144 …-DCMAKE_CXX_FLAGS="-g -O2 -fno-omit-frame-pointer -fsanitize=address -fsanitize=thread -fno-saniti…
189 (libbenchmark.a/.so). If you followed the build steps above, this library will 
190 be under the build directory you created.
193 # Example on linux after running the build steps above. Assumes the
194 # `benchmark` and `build` directories are under the current directory.
195 $ g++ mybenchmark.cc -std=c++11 -isystem benchmark/include \
196   -Lbenchmark/build/src -lbenchmark -lpthread -o mybenchmark
202 The compiled executable will run all benchmarks by default. Pass the `--help`
203 flag for option information or see the [User Guide](docs/user_guide.md).
207 If using CMake, it is recommended to link against the project-provided