aboutsummaryrefslogtreecommitdiff
path: root/lib/googletest/gtest
Commit message (Collapse)AuthorAgeFilesLines
* Remove residual blank line at start of MakefileWarner Losh2024-07-152-2/+0
| | | | | | | This is a residual of the $FreeBSD$ removal. MFC After: 3 days (though I'll just run the command on the branches) Sponsored by: Netflix
* Remove $FreeBSD$: one-line sh patternWarner Losh2023-08-162-2/+0
| | | | Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
* Import GoogleTest 1.14.0Enji Cooper2023-08-101-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | GoogleTest 1.14.0 now requires C++14 to build. Change `googletest.test.inc.mk` to reflect this requirement. Adjust the build integration logic to handle the new version of GoogleTest (add/remove headers/sources as needed). Tighten down warnings via `CXXFLAGS.clang` instead of ignoring all warnings. Some new warnings snuck in after I did my last round of fix submissions upstream. Also address some overlinking added in the previous version import by removing superfluous libraries. =============================== Expect WhenDynamicCastToTest.AmbiguousCast to fail This change reapplies the expected failure from 1.10.0. Ref: https://github.com/google/googletest/issues/2172 MFC after: 2 weeks Reviewed by: asomers, emaste Differential Revision: https://reviews.freebsd.org/D41399 Merge commit '8ef491440fcaec96f899d73e08873426c78583a4' into googletest-v1.14.0-import
* Major improvement to build parallelism for googletest internal testsAlex Richardson2020-10-192-49/+0
| | | | | | | | | | | | | | | | | Currently the googletest internal tests build after the matching library. However, each of these is serialized at the top level makefile. Additionally some of the tests (e.g. the gmock-matches-test) take up to 90 seconds to build with clang -O2. Having to wait for this test to complete before continuing to the next directory seriously slows down the parllelism of a -j32 build. Before this change running `make -C lib/googletest -j32 -s` in buildenv took 202 seconds, now it's 153 due to improved parallelism. Reviewed By: emaste (no objection) Differential Revision: https://reviews.freebsd.org/D26748 Notes: svn path=/head/; revision=366850
* gtest: link against libregex for GNU extensionsKyle Evans2020-08-041-1/+1
| | | | | | | | | | | | gtest tests want to use \w ([[:alnum:]]) at the very least, which was causing them to fail after r363679. Start linking against libregex so that this shorthand is implemented. PR: 248452 Notes: svn path=/head/; revision=363820
* Reword the comment above NO_WERROREnji Cooper2019-02-211-1/+1
| | | | Notes: svn path=/projects/import-googletest-1.8.1/; revision=344424
* Use gmock/gtest headers when PRIVATELIB is definedEnji Cooper2019-02-211-3/+3
| | | | | | | | | | | | The move to /usr/include/private prefixed paths seems to require a bit more effort in order to compile programs. Install the headers to /usr/include/private/g{mock,test}/... and automatically include /usr/include/private in GTESTS_CXXFLAGS to make compilation seamless. I will work on the more global problem later with @bdrewery. Notes: svn path=/projects/import-googletest-1.8.1/; revision=344420
* Build death tests programmaticallyEnji Cooper2019-02-211-8/+9
| | | | | | | | The previous code hardcoded the death test build definitions in a duplicative manner. The new code doesn't. Notes: svn path=/projects/import-googletest-1.8.1/; revision=344416
* Fix gtest test compilation and build more testsEnji Cooper2019-02-201-11/+22
| | | | | | | | | | | | | | | | My previous work to integrate these tests was incomplete/incorrect, because I misunderstood how the cmake macros worked. This addresses items with the gtest tests, which in turn fixes test compilation and adds more tests which I had previously missed. Due to an unknown issue with gtest_stress_test, I had to add pthread to LIBADD, even though I shouldn't have added it to that (it was failing to link -lpthread to libprivategtest.a). Add a XXX comment to note that something's awry there and deserves additional investigation. Notes: svn path=/projects/import-googletest-1.8.1/; revision=344345
* Sprinkle `${HAS_TESTS}` in MakefilesEnji Cooper2019-02-201-1/+2
| | | | | | | While here, reindent `SUBDIR.${MK_TESTS}` Notes: svn path=/projects/import-googletest-1.8.1/; revision=344339
* Use `GTESTS` instead of `PLAIN_TESTS_CXX`Enji Cooper2019-02-201-13/+13
| | | | | | | | | | | The former is from googletest.test.mk, whereas the latter is from plain.test.mk. As noted in r344328, Kyua will adopt more native GoogleTest support. Thus, it's more desirable to make the test interface more of an opaque blackbox for the testcase implementer. Notes: svn path=/projects/import-googletest-1.8.1/; revision=344329
* Compile the tests without -Werror for nowEnji Cooper2019-02-131-0/+3
| | | | | | | I'm working on resolving the issue upstream on github Notes: svn path=/projects/import-googletest-1.8.1/; revision=344087
* Merge build glue for libraries and tests done on githubEnji Cooper2019-02-133-0/+86
I need to doublecheck my work vs the port, but I believe that this covers the initial integration of all upstream tests. Ref: https://github.com/ngie-eign/freebsd/tree/googletest-integration Notes: svn path=/projects/import-googletest-1.8.1/; revision=344086
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-06 04:30:27 +0000