aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/CMakeLists.txt
Commit message (Collapse)AuthorAgeFilesLines
* Googletest exportAbseil Team2020-02-071-1/+0
| | | | | | | | | Get rid of gmock-generated-function-mockers.h and gmock-generated-function-mockers.h.pump. Stop using pump for GMOCK_METHOD* macroses generation. PiperOrigin-RevId: 293454519
* Use -Wa,-mbig-obj for Cygwin/MinGW alwaysAdam Badura2019-08-111-3/+8
|
* Correct CMake to cover CygwinAdam Badura2019-07-271-2/+2
|
* Fix typo introduced in 63be3dcc245 (maintaners -> maintainers)Enji Cooper2019-05-191-1/+1
| | | | Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
* Googletest exportmisterg2019-05-031-0/+3
| | | | | | Clarify build system support - CMake and automake community supported PiperOrigin-RevId: 245821927
* Prefix googletest binaries under its own subtree instead of `gtest`Enji Cooper2019-03-291-1/+1
| | | | | | | | | | | | | | | | | | Building all test binaries under their respective subtrees makes building the project via cmake easier to grok without additional hacks. In particular, when dealing with the conversion I proposed in https://reviews.freebsd.org/D19430 (switching from autotools to cmake), I ran into unexpected gtest prefixing under the googlemock directory, as opposed to the googletest directory. Example: Before: `googlemock/gtest/googletest-break-on-failure-unittest_` After: `googletest/googletest-break-on-failure-unittest_` The latter form is easier to translate to packaging manifests when building googlemock is disabled, as well as enabled, as the path remains consistent when the feature flag is disabled. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
* Googletest exportAbseil Team2019-01-081-1/+0
| | | | | | Drop generated file gmock-generated-internal-utils.h. PiperOrigin-RevId: 228232195
* Googletest exportAbseil Team2018-11-151-0/+1
| | | | | | One macro to rule them all. PiperOrigin-RevId: 221462515
* Unconditionally use std::tuple.Abseil Team2018-10-091-25/+0
| | | | | | Remove all mention of TR1 tuple and our own implementation of tuple. PiperOrigin-RevId: 216395043
* Merge c798e39a4f96f5a985126cc3fab4738b6412cfc1 into ↵Matthieu2018-10-021-0/+14
| | | | | | | | e93da23920e5b6887d6a6a291c3a59f83f5b579e Closes #1836 PiperOrigin-RevId: 215461025
* [msys] pass big object file option to assembler for target gmock-matchers_testMatthieu Longo2018-09-181-0/+3
|
* Use `$<INSTALL_PREFIX>` in `target_include_directories`Dakota Hawkins2018-08-241-2/+2
| | | | | | | | | | | | | | | To make sure packages are relocatable, use `$<INSTALL_PREFIX>` in `$<INSTALL_INTERFACE:...>` `target_include_directories`. `$<INSTALL_PREFIX>` was introduced in CMake 2.8.11, which is already being checked for locally. References: - https://cmake.org/cmake/help/latest/manual/cmake-packages.7.html#id19 - https://github.com/robotology/how-to-export-cpp-library/blob/claudio/headeronly/src/LibTemplateCMake/CMakeLists.txt#L42 Signed-off-by: Dakota Hawkins <dakotahawkins@gmail.com>
* Install CMake export filesStefano Soffia2018-08-221-65/+19
| | | | Rework of the closed pull request #768
* Improve CMake exported targets.Dakota Hawkins2018-08-211-6/+33
| | | | | | | | | | | I _think_ this represents some of the "best practices" for exporting targets. They'll be available in a `googletest::` namespace (e.g. `googletest::gmock`) with non-namespaced `ALIAS` targets. - Added GOOGLETEST_VERSION variable - Use `CMakePackageConfigHelpers`, bump minimum CMake version to 2.8.8 Signed-off-by: Dakota Hawkins <dakotahawkins@gmail.com>
* Merge branch 'master' into cleanup-cmakeGennadiy Civil2018-08-151-3/+3
|\
| * Change location of generated pkg-config files from CMAKE_BINARY_DIR to ↵Elias Daler2018-08-131-3/+3
| | | | | | | | gmock/gtest_BINARY_DIR (#1717)
* | Clean up cache non-advanced variable for subprojectHenry Fredrick Schreiner2018-04-051-4/+14
|/
* Merge branch 'master' into fix-core-dump-sharedGennadiy Civil2018-01-091-7/+7
|\
| * remove extra lineBryan Zimmerman2017-12-111-1/+0
| |
| * Merge branch 'master' into masterbryanzim2017-12-111-2/+2
| |\
| | * Merge branch 'master' into use-system-includesGennadiy Civil2017-12-081-0/+2
| | |\
| | * | make includes systemSam Lunt2017-11-271-2/+2
| | | |
| * | | Merge branch 'master' into masterbryanzim2017-12-081-1/+2
| |\ \ \ | | | |/ | | |/|
| * | | fix for VS2017 deprecation of ::tr1::tupleBryan Zimmerman2017-10-271-5/+7
| | |/ | |/| | | | | | | | | | change static_cast to ImplicitCast_ for consitency fixes for building with path names containing spaces
* | | Merge branch 'master' into fix-core-dump-sharedGennadiy Civil2017-12-081-0/+2
|\ \ \ | | |/ | |/|
| * | Improved description of VS std::tuple supportWojciech Mamrak2017-12-071-0/+2
| |/
* / Fix double free when building Gtest/GMock in shared libraries and linking a ↵Romain Geissler2017-12-021-23/+40
|/ | | | test executable with both.
* CMake: use threads if allowed and found, not just if found.Roman Lebedev2017-09-011-1/+1
| | | | | | | | | | | | | | | | | | If the user's cmakelists.txt first look for threads using find_package(Threads), then set(gtest_disable_pthreads ON), and then include googletest. GoogleTest will not look for threads. But since they have already been found before in user's cmakelists, it will use them regardless. This helped me fix build issue in darktable-org/rawspeed on windows/MSYS2, even though there are threads, and they are usable, googletest build was failing with issues about AutoHandle. I was first looking for threads, and only then including googletest, so no matter the value of gtest_disable_pthreads, it failed. The other obvious solution is for user to first include googletest, and only then look for threads by himself.
* Add support for pkgconfigDavid Seifert2017-08-141-1/+18
|
* Merge pull request #1160 from mwoehlke-kitware/honor-lib_suffixGennadiy Civil2017-08-111-4/+8
|\ | | | | Fix library install destinations
| * Fix library install destinationsMatthew Woehlke2017-08-091-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Modify library install destinations to install .dll's to the correct location (`bin`, not `lib`), and to install other artifacts to the correct platform-dependent location by using GNUInstallDirs. This is required for some distributions (e.g. Fedora) and will fix an issue that otherwise requires those distributions to patch the upstream sources. Also, add options to suppress installation, which may be useful for projects that embed Google Test. Since Google Test is trying to support archaic versions of CMake, a brain-dead fallback (which requires that the user set either LIB_SUFFIX or CMAKE_INSTALL_LIBDIR themselves) is included for versions that predate GNUInstallDirs. Fixes #1161. Co-Authored-By: d3x0r <d3x0r@users.noreply.github.com>
* | 2.6.4 is the minimum CMake version, so enforce it (#656)Craig Scott2016-12-171-1/+1
|/
* Merge pull request #657 from audiofanatic/issue655-targetHeaderDepsBilly Donahue2015-12-101-0/+8
|\ | | | | Add include dirs to targets if CMake version supports it
| * Add include dirs to targets if CMake version supports itCraig Scott2015-12-061-0/+8
| |
* | Added CMake install rules for GMockJoan Puigcerver2015-12-031-0/+8
|/
* googlemock: fix unified buildArnaud Lacombe2015-08-261-1/+1
|
* move googlemock files into googlemock/ subdirBilly Donahue2015-08-251-0/+186
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-09 07:18:49 +0000