Warnings when compiling with Visual Studio 2008
Closed this issue · 6 comments
GoogleCodeExporter commented
Can compile with VS 2008
Original issue reported on code.google.com by kasaj...@gmail.com on 11 Mar 2010 at 4:52
GoogleCodeExporter commented
Please be specific about which version of googlemock you are using, and what
warning
messages you are getting.
Original comment by w...@google.com on 11 Mar 2010 at 5:38
GoogleCodeExporter commented
I'm using the latest version of GoogleMocks, which ships with VS2005 projects.
The warnings have to do with
deprecated command line arguments, but I suspect that this more than just "fix
this one error". This is more of a
feature, where GoogleMocks should really support and include a VS2008 tested
version.
Original comment by kasaj...@gmail.com on 11 Mar 2010 at 5:10
GoogleCodeExporter commented
We don't want to provide VS projects for multiple VS versions, as that's hard to
maintain and bloats the distribution package.
We are switching the build system to cmake soon, so the issue will become
obsolete.
Original comment by w...@google.com on 12 Mar 2010 at 7:06
- Changed state: WontFix
- Added labels: OpSys-Windows, Priority-Low, Type-Enhancement
- Removed labels: Priority-Medium, Type-Defect
GoogleCodeExporter commented
I understand what you're saying.
There's another part of this that's not related to supplying a Visual Studio
2008 project, and that's making sure
the code compiles with 2008 without warnings. You can make that change to the
source code, and that's
unrelated to whether you deliver just Visual Studio 2005 solutions or switch
everything to cmake.
Original comment by kasaj...@gmail.com on 12 Mar 2010 at 5:46
GoogleCodeExporter commented
The version in the trunk is warning free when we tested it. If you see
warnings from
that version (not 1.4.0), please provide the complete and *exact* compiler
messages
you see. Thanks.
Original comment by w...@google.com on 13 Mar 2010 at 12:57
GoogleCodeExporter commented
Okay, I missed that subtlety. I thought that we could log bugs against the
current
release, not what's in the latest trunk. So sorry.
I'll try the latest build.
Original comment by kasaj...@gmail.com on 13 Mar 2010 at 1:00