google / benchmark / 2118

92%

push

travis-ci

<a href="https://github.com/google/benchmark/commit/<a class=hub.com/google/benchmark/commit/4b771940329acf371037e55b88730cdf9fbe391e">4b7719403<a href="https://github.com/google/benchmark/commit/4b771940329acf371037e55b88730cdf9fbe391e">&quot;&gt;CMake: codedrop of googletest cmake magic from me (#809)

https://github.com/google/benchmark/pull/801 is stuck with some cryptic cmake failure due to
some linking issue between googletest and threading libraries.

I suspect that is mostly happening because of the, uhm,
intentionally extremely twisted-in-the-brains approach that is being used to
actually build the library as part of the buiild,
except without actually building it as part of the build.

If we do actually build it as part of the build,
then all the transitive dependencies should magically be in order,
and maybe everything will just work.

This new version of cmake magic was written by me in
https://github.com/darktable-org/rawspeed/blob/&lt;/a&gt;&lt;a class=&quot;double-link&quot; href=&quot;https://github.com/google/benchmark/commit/&lt;a class=&quot;double-link&quot; href=&quot;https://git">&lt;a class=</a>hub.com/google/benchmark/commit/<a class=hub.com/google/benchmark/commit/0e22f085c57cd629983c7351c598abd744b421b5">0e22f085c">0e22f085c</a><a href="https://github.com/google/benchmark/commit/4b771940329acf371037e55b88730cdf9fbe391e">/cmake/Modules/GoogleTest.cmake.in
https://github.com/darktable-org/rawspeed/blob/0e22f085c57cd629983c7351c598abd744b421b5/cmake/Modules/GoogleTest.cmake, based on the official googletest docs and LOTS of experimentation.</a>

1771 of 1931 relevant lines covered (91.71%)

5221312.39 hits per line