Add nasm support to Chromium, use it for boringssl.
I'll switch ffmpeg over in a future CL since it seems to need some
work before it's ready to go.
Per davidben at chromium.org who originally authored this update
on https://chromium-review.googlesource.com/c/chromium/src/+/1119211:
Yasm has been unmaintained for a few years, while NASM is actively
maintained. Yasm is already missing some of the newer Intel
instructions, and will continue to miss newer ones. Additionally,
BoringSSL gets its assembly from OpenSSL which natively tests with NASM,
not Yasm, so using NASM puts us closer to the tested path.
BUG=766721
TEST=CQ is happy
R=brucedawson, davidben
Change-Id: Ifa49686e2985967c19b7fc91f94ef6350038fb7c
Reviewed-on: https://chromium-review.googlesource.com/c/1313832
Commit-Queue: Dale Curtis <[email protected]>
Reviewed-by: Bruce Dawson <[email protected]>
Reviewed-by: David Benjamin <[email protected]>
Cr-Commit-Position: refs/heads/master@{#606271}diff --git a/DEPS b/DEPS
index 82b55e9..4d359b7af 100644
--- a/DEPS
+++ b/DEPS
@@ -961,6 +961,11 @@
'condition': 'checkout_nacl and checkout_win',
},
+ 'src/third_party/nasm': {
+ 'url': Var('chromium_git') + '/chromium/deps/nasm.git' + '@' +
+ '20920a85609b0608d4c9c80b525196d07183b289'
+ },
+
'src/third_party/netty-tcnative/src': {
'url': Var('chromium_git') + '/external/netty-tcnative.git' + '@' + '5b46a8ef4a39c39c576fcdaaf718b585d75df463',
'condition': 'checkout_android',
