gtest-md.vcproj produces gtest.lib rather than gtest-md.lib (inconsistent naming)

asteever / thirdparty_gtest

Automatically exported from code.google.com/p/googletest

BSD 3-Clause "New" or "Revised" License

0 stars 0 forks source link

gtest-md.vcproj produces gtest.lib rather than gtest-md.lib (inconsistent naming) #300

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

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 case.

Original issue reported on code.google.com by gusver...@gmail.com on 9 Jul 2010 at 2:36

GoogleCodeExporter commented 9 years ago

Original comment by w...@google.com on 22 Jul 2010 at 4:49

Changed state: Accepted
Added labels: OpSys-Windows, Priority-Low, Type-Enhancement, Usability
Removed labels: Priority-Medium, Type-Defect

GoogleCodeExporter commented 9 years ago

What do you think, Vlad?

Original comment by w...@google.com on 27 Sep 2010 at 7:24

GoogleCodeExporter commented 9 years ago

It was somewhat unexpected that the gtest-md project did not follow this while 
the gtest-main-md did follow it.
Usually .lib files are kept in the same directory so it might prove useful to 
add it.

If this is going to be changed, it would be nice to have the .lib files all 
output in one directory for example: $(SolutionDir)bin

Original comment by learn0more on 17 Apr 2014 at 5:20