| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
658c6390a5b363f46c6ad448ad1bce9d6e97e53a
Closes #1893
PiperOrigin-RevId: 216712426
|
|/
|
|
|
|
|
| |
Using absolute paths in the pkg-config file makes it not relocatable and
leads to problems, when trying to use it with precompiled cross
toolchains. Setting prefix to relative path based on pcfiledir makes it
more reliable for such cases.
|
|
|
|
|
|
| |
Remove all mention of TR1 tuple and our own implementation of tuple.
PiperOrigin-RevId: 216395043
|
|
|
|
|
|
|
|
| |
e93da23920e5b6887d6a6a291c3a59f83f5b579e
Closes #1836
PiperOrigin-RevId: 215461025
|
|\ |
|
| |
| |
| |
| | |
Rework of the closed pull request #768
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This prevents warning D9025 (one command-line option overrides
another) on MSVC builds: some test targets are built with
the /EHs-c- which conflicts with /EHsc.
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
nested cmake project,
which breaks my build as gcc does not allow -specs=nosys.specs to be called multiple times.
Removing this fixes it and seems to keep the same compile options, just removing the duplicate definition.
|
|\ \ |
|
| | | |
|
| |/
| |
| |
| |
| | |
This does the same thing to the CMake tests that is done to the
Bazel tests, and now makes the CMake tests pass.
|
| |\ |
|
| | |\ |
|
| | | | |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
CMAKE_DEBUG_POSTFIX is a global configuration parameter, and
changing it pollutes the configuration space for other projects
that enclose this project.
DEBUG_POSTFIX is better to use since it is a target-specific poperty.
Fixes #1334
Fixes #1268
|
| |/ |
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |/ |
|
| |
| |
| |
| | |
generators
|
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 73d58dd4c83883b46697798e978d576b28b1d24e.
Unfortunately, ${CMAKE_CFG_INTDIR} is set during build only and doesn't
help here.
|
| |
| |
| |
| |
| |
| |
| | |
On single-configuration build systems as Makefile Generators, there is
no subdirectory for the configuration in the build tree - therefore ask
cmake for the subdir by using CMAKE_CFG_INTDIR, which is just '.' on
single-configuration build systems (Linux et al.).
|
| | |
|
| | |
|
|/
|
|
|
| |
Replaced legacy syntax of cmake add_test() with more modern syntax.
This allows running gtests's own tests on remote (cross) systems
using CMAKE_CROSSCOMPILING_EMULATOR with cmake-3.3 or newer.
|
|\
| |
| | |
Fix compilation of googletest with MinGW using Win32 threads
|
| |
| |
| |
| | |
It's not supported, and native Windows threading is available for MinGW
|
|/ |
|
|
|