Closed GoogleCodeExporter closed 8 years ago
For libyuv the build is
gn gen out/Release "--args=is_debug=false target_cpu=\"x86\""
ninja -C out/Release
Original comment by fbarch...@chromium.org
on 4 Nov 2015 at 6:55
The following revision refers to this bug:
https://chromium.googlesource.com/libyuv/libyuv.git/+/c2bff1a1af3933c866673c8184e635495d648739
commit c2bff1a1af3933c866673c8184e635495d648739
Author: Frank Barchard <fbarchard@google.com>
Date: Wed Nov 04 19:09:00 2015
add .gn file for gn builds
using a stripped down gn file from webrtc.
BUG=libyuv:411,libyuv:519
R=kjellander@chromium.org
Review URL: https://codereview.chromium.org/1417613007 .
[modify] http://crrev.com/c2bff1a1af3933c866673c8184e635495d648739/.gitignore
[add] http://crrev.com/c2bff1a1af3933c866673c8184e635495d648739/.gn
[modify]
http://crrev.com/c2bff1a1af3933c866673c8184e635495d648739/README.chromium
[modify]
http://crrev.com/c2bff1a1af3933c866673c8184e635495d648739/include/libyuv/version
.h
Original comment by bugdroid1@chromium.org
on 4 Nov 2015 at 7:10
gn gen out/Release "--args=is_debug=false target_cpu=\"x86\""
Done. Wrote 2775 targets from 834 files in 1615ms
Done. Wrote 2775 targets from 834 files in 1645ms
ninja: Entering directory `out\Release'
[9/11] CXX obj/media/base/perftests/yuv_convert_perftest.obj
FAILED: ninja -t msvc -e environment.x86 --
"c:\src\depot_tools\win_toolchain\vs2013_files\VC\bin\amd64_x86/cl.exe" /nologo
/showIncludes /FC @obj/media/base/perftests/yu
v_convert_perftest.obj.rsp /c ../../media/base/yuv_convert_perftest.cc
/Foobj/media/base/perftests/yuv_convert_perftest.obj
/Fdobj/media/base/perftests_cc.pdb
d:\src\chrome\src\third_party\libyuv\include\libyuv\row.h(16) : fatal error
C1083: Cannot open include file: 'libyuv/basic_types.h': No such file or
directory
ninja: build stopped: subcommand failed.
ninja: Entering directory `out\Release'
[2/2] LINK media_unittests.exe
Original comment by fbarch...@chromium.org
on 5 Nov 2015 at 7:19
Original comment by fbarch...@chromium.org
on 6 Nov 2015 at 1:47
Original issue reported on code.google.com by
fbarch...@chromium.org
on 4 Nov 2015 at 6:30