Open GoogleCodeExporter opened 9 years ago
Test of 32 bit Windows build
With GN
call gn gen out/Release "--args=is_debug=false target_cpu=\"x86\""
call gn gen out/Debug "--args=is_debug=true target_cpu=\"x86\""
ninja -C out/Release
ninja -C out/Debug
21.95 seconds
With GYP
set GYP_DEFINES=target_arch=ia32 libyuv_enable_svn=1
call python gyp_libyuv -fninja -G msvs_version=2013 libyuv_test.gyp
ninja -C out\Debug
ninja -C out\Release
24.97 seconds
Original comment by fbarch...@google.com
on 10 Mar 2015 at 5:28
Updated Getting Started for Windows
https://code.google.com/p/libyuv/wiki/GettingStarted
Original comment by fbarch...@chromium.org
on 20 Mar 2015 at 10:39
Does GN support different compilers? vs2015 vs clang vs vs2013?
Original comment by fbarch...@google.com
on 9 May 2015 at 2:40
dpranke: do you know the answer to #3 above?
Original comment by kjellan...@google.com
on 10 May 2015 at 1:30
I don't think the win GN build supports clang yet.I believe vs2015 vs. vs2013
*might* work, but I haven't tested it (we use pretty much the same underlying
scripts to setup the toolchain for GN that we do for GYP).
I would cc' thakis and scottmg if I had edit rights on this :).
Original comment by dpra...@google.com
on 11 May 2015 at 11:28
+thakis, scottmg: Can you provide more info on #3 above?
Original comment by kjellan...@google.com
on 12 May 2015 at 6:29
No one that I know of has tested GN-clang. Even gyp-clang is still
non-mainstream on Windows.
I would guess that vs2015 "might" work too. The compiler is not yet shipped,
and there's no bots testing chrome. So if it works, it's by chance, and if it
breaks, you get both pieces (for now).
Original comment by scottmg@chromium.org
on 12 May 2015 at 4:56
clang/win doesn't work in GN yet (see also the caveats at
https://code.google.com/p/chromium/wiki/Clang#Windows ). I do want to look at
that soon though.
Original comment by thakis@chromium.org
on 12 May 2015 at 6:57
Original issue reported on code.google.com by
fbarch...@google.com
on 10 Mar 2015 at 4:52