Lines Matching +full:release +full:- +full:version

3 …-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https://github…
6 …st-bindings](https://github.com/google/benchmark/workflows/test-bindings/badge.svg)](https://githu…
40 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss)
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
79 $ cmake -E make_directory "build"
81 $ cmake -E chdir "build" cmake -DBENCHMARK_DOWNLOAD_DEPENDENCIES=on -DCMAKE_BUILD_TYPE=Release ../
83 # cmake -DCMAKE_BUILD_TYPE=Release -S . -B "build"
85 $ cmake --build "build" --config Release
103 $ cmake -E chdir "build" ctest --build-config Release
109 sudo cmake --build "build" --config Release --target install
116 * Otherwise, if `-DBENCHMARK_DOWNLOAD_DEPENDENCIES=ON` is specified during
120 If you do not wish to build and run the tests, add `-DBENCHMARK_ENABLE_GTEST_TESTS=OFF`
123 ### Debug vs Release
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
132 To enable link-time optimisation, also add `-DBENCHMARK_ENABLE_LTO=true` when
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…
149 The main branch contains the latest stable version of the benchmarking library;
151 being made only upon the release of a new major version.
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`
207 If using CMake, it is recommended to link against the project-provided
210 It is possible to use ```find_package``` to import an installed version of the