| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
The one large test does not link in limited memory environments
Closes #3653
PiperOrigin-RevId: 436753193
Change-Id: Idd59b6509994fc642147b88279ee791cd1d7bdd0
|
| |
|
|
|
|
|
|
|
| |
On QNX, pthread is part of libc [1]. There's no separate pthread library
to link.
[1] https://www.qnx.com/developers/docs/7.1/index.html#com.qnx.doc.neutrino.lib_ref/topic/p/pthread_create.html
|
|
|
|
|
|
|
|
| |
Updates Linux docker image to use Bazel 4.1.0 and GCC 11.1
Updates Bazel dependencies
Removes the last usage of the deprecated and removed Python2
PiperOrigin-RevId: 375759184
|
|
|
|
|
|
| |
Format WORKSPACE and googlemock/test/BUILD.bazel using buildifier
PiperOrigin-RevId: 360913861
|
|
|
|
|
|
| |
Internal Change
PiperOrigin-RevId: 347631521
|
|
|
|
|
|
| |
Fix a missing Bazel build dependency
PiperOrigin-RevId: 346783462
|
|
|
|
|
|
| |
Internal change
PiperOrigin-RevId: 299345492
|
|
|
|
|
|
| |
Fixes googletest for upcoming `--incompatible_load_cc_rules_from_bzl` (https://github.com/bazelbuild/bazel/issues/8743) and `--incompatible_load_python_rules_from_bzl` (https://github.com/bazelbuild/bazel/issues/9006).
This change was automatically generated with `buildifier -lint=fix -warnings=all $(find . -name "BUILD" -o -name "BUILD.bazel" -o -name "*.bzl")`.
|
|
|
|
|
|
| |
gmock_output_test has to run under python2. Bazel 0.27.0 causes this test to break. Fixing it.
PiperOrigin-RevId: 253820111
|
|
|
|
|
|
|
|
| |
Improve Bazel build files.
New target gtest_prod allows access to the FRIEND_TEST macro without depending on the entirety of GTest in production executables. Additionally, duplicate config_setting rules were removed and formatting was adjusted.
PiperOrigin-RevId: 220279205
|
|
|
|
| |
PiperOrigin-RevId: 216423319
|
|
|
|
| |
PiperOrigin-RevId: 216417182
|
| |
|
|
|
|
| |
and x64_windows_msvc
|
|
|
|
|
| |
Without the directive embedding googletest into third_party breaks
any //... target.
|
| |
|
|
|