search

leetaizhu / libyuv

Automatically exported from code.google.com/p/libyuv
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

vs2015 64 bit build break #441

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
c:\src\libyuv2\trunk>ninja -C out\Debug_x64
ninja: Entering directory `out\Debug_x64'
[2/9] CC obj\third_party\libjpeg_turbo\simd\libjpeg.jsimd_i386.obj
FAILED: ninja -t msvc -e environment.x64 -- "C:\Program Files (x86)\Microsoft 
Visual Studio 14.0\VC\bin\amd64\cl.exe" /nologo /showIncludes /FC 
@obj\third_party
\libjpeg_turbo\simd\libjpeg.jsimd_i386.obj.rsp /c 
..\..\third_party\libjpeg_turbo\simd\jsimd_i386.c 
/Foobj\third_party\libjpeg_turbo\simd\libjpeg.jsimd_i386.obj
 /Fdobj\third_party\libjpeg_turbo\libjpeg.c.pdb
c:\src\libyuv2\trunk\third_party\libjpeg_turbo\simd\jsimd_i386.c(79): error 
C2220: warning treated as error - no 'object' file generated
c:\src\libyuv2\trunk\third_party\libjpeg_turbo\simd\jsimd_i386.c(79): warning 
C4311: 'type cast': pointer truncation from 'const int [0]' to 'unsigned int'
c:\src\libyuv2\trunk\third_party\libjpeg_turbo\simd\jsimd_i386.c(102): warning 
C4311: 'type cast': pointer truncation from 'const int [0]' to 'unsigned int'
c:\src\libyuv2\trunk\third_party\libjpeg_turbo\simd\jsimd_i386.c(124): warning 
C4311: 'type cast': pointer truncation from 'const int [0]' to 'unsigned int'
c:\src\libyuv2\trunk\third_party\libjpeg_turbo\simd\jsimd_i386.c(178): warning 
C4311: 'type cast': pointer truncation from 'const int [0]' to 'unsigned int'

Original issue reported on code.google.com by fbarch...@chromium.org on 14 May 2015 at 5:05

GoogleCodeExporter commented 9 years ago 
A work around is disable the warning, or disable jpeg.

set GYP_DEFINES=buildtype=Official target_arch=x64 libyuv_enable_svn=1 
libyuv_disable_jpeg=1
call python gyp_libyuv -fninja -Gconfig=Release_x64 -Gmsvs_version=2015 
libyuv_test.gyp
ninja -C out\Release_x64

Original comment by fbarch...@chromium.org on 15 May 2015 at 1:07

GoogleCodeExporter commented 9 years ago

Original comment by fbarch...@chromium.org on 15 May 2015 at 6:03

GoogleCodeExporter commented 9 years ago 
Wrong bug number for the blocking chromium issue. It should be 440500.

Original comment by brucedaw...@chromium.org on 15 May 2015 at 6:09

GoogleCodeExporter commented 9 years ago

Original comment by fbarch...@chromium.org on 19 May 2015 at 12:41

GoogleCodeExporter commented 9 years ago 
I'm unable to repro?
The source code in jpeg casts a pointer to an int and then checks if its a 
multiple of 16.  Its safe enough and used to cause a warning, and now doesnt.
Closing as invalid.

Original comment by fbarch...@chromium.org on 19 May 2015 at 1:34