Remove //crypto:platform
//crypto:platform historically abstracted between NSS and OpenSSL, back
when we used one or the other depending on configuration. It then then
got copy-pasted everywhere as targets split, folks got deps vs.
public_deps wrong, or code moved around.
Now we always use //third_party/boringssl for cryptography and TLS. On
Linux and CrOS, we additionally use //build/config/linux/nss for some
certificate-related platform integration points, though we're gradually
moving away from it.
Replace uses of //crypto:platform with one, the other, both, or often
neither. For lower-level targets, I greped for use of NSS and BoringSSL
headers and depended on the one that was used. For top-level targets in
//chrome/browser, it gets a bit of a mess and probably not worth
manually revising, so I just let public_deps, etc., flow.
Fixed: 1275165
Change-Id: Ib48e6a9ed7b6a3893834afe0d6da1cffde7e374f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3602624
Reviewed-by: Colin Blundell <[email protected]>
Reviewed-by: Reilly Grant <[email protected]>
Reviewed-by: Kentaro Hara <[email protected]>
Reviewed-by: Sergey Volk <[email protected]>
Commit-Queue: David Benjamin <[email protected]>
Reviewed-by: Dale Curtis <[email protected]>
Reviewed-by: Matt Mueller <[email protected]>
Reviewed-by: Steven Bennetts <[email protected]>
Cr-Commit-Position: refs/heads/main@{#997748}
diff --git a/chrome/browser/BUILD.gn b/chrome/browser/BUILD.gn
index a937f1dc..eb144d25 100644
--- a/chrome/browser/BUILD.gn
+++ b/chrome/browser/BUILD.gn
@@ -2333,7 +2333,6 @@
"//content/public/browser",
"//content/public/common",
"//crypto",
- "//crypto:platform",
"//device/base",
"//device/base/synchronization",
"//device/fido",
@@ -7384,6 +7383,7 @@
if (is_linux) {
sources += [ "net/nss_service_linux.cc" ]
}
+ configs += [ "//build/config/linux/nss" ]
}
if (trial_comparison_cert_verifier_supported) {
