-
```
In version 1.5.0, compare the OutputFile property in gtest-md.vcproj and
gtest_main-md.vcproj
I expect the lib names to be consistent using the project name. Both libs
ending in -md in this cas…
-
```
In version 1.5.0, compare the OutputFile property in gtest-md.vcproj and
gtest_main-md.vcproj
I expect the lib names to be consistent using the project name. Both libs
ending in -md in this cas…
-
```
Change environment variables to command line parameters.
```
Original issue reported on code.google.com by `fbarch...@chromium.org` on 16 Oct 2015 at 5:45
-
Get gtest and ros gtest infrastructure working on windows.
-
### Describe the issue
Problem:
With the latest version of Xcode 15.3 it is no longer possible to use chrono timpoints in a test assertion, if the build target is lower than macOS 13.3. With Xcode 1…
-
```
In version 1.5.0, compare the OutputFile property in gtest-md.vcproj and
gtest_main-md.vcproj
I expect the lib names to be consistent using the project name. Both libs
ending in -md in this cas…
-
```
In version 1.5.0, compare the OutputFile property in gtest-md.vcproj and
gtest_main-md.vcproj
I expect the lib names to be consistent using the project name. Both libs
ending in -md in this cas…
-
```
In version 1.5.0, compare the OutputFile property in gtest-md.vcproj and
gtest_main-md.vcproj
I expect the lib names to be consistent using the project name. Both libs
ending in -md in this cas…
-
```
In version 1.5.0, compare the OutputFile property in gtest-md.vcproj and
gtest_main-md.vcproj
I expect the lib names to be consistent using the project name. Both libs
ending in -md in this cas…
-
```
In version 1.5.0, compare the OutputFile property in gtest-md.vcproj and
gtest_main-md.vcproj
I expect the lib names to be consistent using the project name. Both libs
ending in -md in this cas…