Warnings in Visual Studio 2010 and unable to compile unit test

[GoogleCodeExporter]

Warnings in Visual Studio 2010 and unable to compile unit test

[GoogleCodeExporter]

Thanks for the report. Would you maybe mind trying the build of the gflags 
library using CMake to generate the Visual Studio project files ? You may 
indeed still get similar errors, but I would like to continue the development 
of gflags based on this migrated source tree. If you find a fix for these 
warnings and errors that would be great. The plan is to replace the current SVN 
trunk by this new Git branch before the end of this year.

See https://github.com/schuhschuh/gflags/tree/cmake-migration

Original comment by [email protected] on 23 Nov 2013 at 11:16

• Changed title: Warnings in Visual Studio 2010 and unable to compile unit test

[GoogleCodeExporter]

Hi, I'm the same guy who contributed the visual studio fixes on Github 
(@Photonios). I actually just switched my development environment to Windows, 
but I'm setting up a VM for Windows development. I'll give the branch a try 
within a few days. I'll keep your updated.

Original comment by [email protected] on 28 Nov 2013 at 8:49

[GoogleCodeExporter]

* switch development environment to Linux

Original comment by [email protected] on 28 Nov 2013 at 8:49

[GoogleCodeExporter]

Yes, that would be great. I am actually at the moment without my Windows VM, so 
would have difficulties to test myself. Thus it would be helpful if you try it 
out and let me know what you find.

Original comment by [email protected] on 28 Nov 2013 at 11:28

[GoogleCodeExporter]

Any updates on this issue? I have Visual Studio 2013 (12.0) on Windows 7 64-bit 
and I'm getting many build errors. The attached log file is from building the 
"gflags" project on "Release" configuration using the CMake branch.

I would love to help out in getting those issues fixed, but it would be good to 
know if someone else has made some progress so I wouldn't have to duplicate 
effort.

Thanks!

Original comment by [email protected] on 14 Feb 2014 at 1:14

Attachments:

• log.txt

[GoogleCodeExporter]

It seems like nobody looked into these errors and warnings further. I would 
appreciate a patch/pull request for the code in the CMake branch to resolve 
these build errors.

Cheers, Andreas.

Original comment by [email protected] on 13 Mar 2014 at 10:02

[GoogleCodeExporter]

I recall looking at those issues when working on the leak fix branch. Maybe it 
was only for VS2012?

Original comment by [email protected] on 13 Mar 2014 at 3:57

[GoogleCodeExporter]

The build of the Git cmake-migration branch should be fixed now for 
Windows/Visual Studio users (see 
https://github.com/schuhschuh/gflags/commit/b2180eb52c961b20c7b79425ecb9f9773317
c7f7).

Warnings regarding the missing export of STL classes are still present. Will 
look into this next. Some information can be found at 
http://support.microsoft.com/default.aspx?scid=KB;EN-US;168958 .

Original comment by [email protected] on 14 Mar 2014 at 3:33

• Changed state: Started

[GoogleCodeExporter]

The missing STL export warnings are fixed in the cmake-migration branch.

See 
https://github.com/schuhschuh/gflags/commit/70eac23c1b20da94100b2c62081572d80c47
ef0b

Original comment by [email protected] on 14 Mar 2014 at 4:10

• Changed state: Fixed

[GoogleCodeExporter]

The final fix was to simply not export the CommandLineInfo data only structure 
which is fully defined in the header file. Exporting the STL classes will only 
cause more troubles.

Original comment by [email protected] on 20 Mar 2014 at 4:08

• Added labels: Milestone-v2.1