Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build error with VS 2015 #58

Closed
tdenniston opened this issue Apr 8, 2016 · 4 comments
Closed

Build error with VS 2015 #58

tdenniston opened this issue Apr 8, 2016 · 4 comments

Comments

@tdenniston
Copy link
Contributor

I'm seeing a build error with Visual Studio 2015 Update 2 (community edition) on 64-bit Windows 7.

"C:\...\SkiaSharp\native-builds\libskia_windows\libskia_windows_x64.sln" (Build target) (1) ->
"C:\...\SkiaSharp\skia\out\gyp\core.vcxproj" (default target) (6) ->
(ClCompile target) ->
  ..\..\src\core\SkVarAlloc.cpp(48): warning C4334: '<<': result of 32-bit shift implicitly converted to 64 bits
(was 64-bit shift intended?) [C:\...\SkiaSharp\skia\out\gyp\core.vcxproj]

And the build doesn't complete:

 ..\..\src\core\SkVarAlloc.cpp(48): error C2220: warning treated as error

Some searching around turned up this skia upstream bug: https://bugs.chromium.org/p/chromium/issues/detail?id=593448. I don't think it's been fixed upstream yet, but they have identified a workaround, which is to suppress warning C4334.

By applying the following patch in skia, this issue is resolved:

diff --git a/gyp/common_conditions.gypi b/gyp/common_conditions.gypi
index cf43271..3cc5dfb 100644
--- a/gyp/common_conditions.gypi
+++ b/gyp/common_conditions.gypi
@@ -54,6 +54,7 @@
             4275,  # An exported class was derived from a class that was not ex
             4345,  # This is an FYI about a behavior change from long ago. Chro
             4355,  # 'this' used in base member initializer list. Off by defaul
+            4334,
         ],
         'msvs_cygwin_shell': 0,
         'msvs_settings': {

I don't know that this should be an open issue on SkiaSharp, but I figured it was worth documenting so others don't have to duplicate the effort.

@bholmes
Copy link
Contributor

bholmes commented Apr 8, 2016

@mattleibow One for you to consider. Have you hit this?

@mattleibow
Copy link
Contributor

I just hit it after updating to Update 2...

@mattleibow
Copy link
Contributor

I think I will leave this for Google to fix as it is in a few places. However, to work around it, I build in Release mode.

@newky2k
Copy link
Contributor

newky2k commented Nov 14, 2018

closing

@newky2k newky2k closed this as completed Nov 14, 2018
Triage automation moved this from New to Complete / Invalid Nov 14, 2018
@ghost ghost locked as resolved and limited conversation to collaborators Aug 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Triage
  
Done
Development

No branches or pull requests

5 participants