watery01 / libyuv

Automatically exported from code.google.com/p/libyuv
0 stars 0 forks source link

64 bit ninja build fails on jpeg #178

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.
>ninja -C out\Debug_x64

What is the expected output?

success

What do you see instead?

ninja: Entering directory `out\Debug_x64'
[134/136] LIB obj\third_party\libjpeg_turbo\libjpeg.lib
FAILED: c:\bin\depot_tools\python_bin\python.exe gyp-win-tool link-wrapper 
environment.x64 lib.exe /nologo /ignore:4221 /OUT:obj\thi
rd_party\libjpeg_turbo\libjpeg.lib 
@obj\third_party\libjpeg_turbo\libjpeg.lib.rsp
gen\third_party\libjpeg_turbo\jccolmmx.obj : fatal error LNK1112: module 
machine type 'X86' conflicts with target machine type 'x64'

[134/136] CXX obj\unit_test\libyuv_unittest.convert_test.obj
ninja: build stopped: subcommand failed.

Please use labels and text to provide additional information.
Using head chromium deps:
"chromium_revision": "177952",

Original issue reported on code.google.com by fbarch...@google.com on 21 Jan 2013 at 8:12

GoogleCodeExporter commented 9 years ago
It works on Windows.  Here are instructions

set GYP_DEFINES=target_arch=ia32
call python build\gyp_chromium -fninja -G msvs_version=2012 --depth=. 
libyuv_test.gyp
ninja -C out\Debug
ninja -C out\Release

set GYP_DEFINES=target_arch=x64
call python build\gyp_chromium -fninja -G msvs_version=2012 --depth=. 
libyuv_test.gyp
ninja -C out\Debug_x64
ninja -C out\Release_x64

Original comment by fbarch...@google.com on 21 Feb 2013 at 1:28