From 4229ed54eee27211cfa6e34840e8c3bcbefdb582 Mon Sep 17 00:00:00 2001 From: davidben Date: Wed, 8 Jul 2015 09:30:53 -0700 Subject: [PATCH] Don't initialize NSS in Cast renderers for the chimera build. Cast has no need for NSS in renderers apart from the common crypto bits (WebCrypto, //crypto), both of which will be BoringSSL in the chimera. Prepare for that be switching to !USE_OPENSSL rather than USE_NSS_CERTS. BUG=506323 Review URL: https://codereview.chromium.org/1222193007 Cr-Commit-Position: refs/heads/master@{#337835} --- chromecast/renderer/cast_content_renderer_client.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chromecast/renderer/cast_content_renderer_client.cc b/chromecast/renderer/cast_content_renderer_client.cc index 4837dab3003d..1f7c4a68d196 100644 --- a/chromecast/renderer/cast_content_renderer_client.cc +++ b/chromecast/renderer/cast_content_renderer_client.cc @@ -114,7 +114,7 @@ CastContentRendererClient::GetRendererMessageFilters() { void CastContentRendererClient::RenderThreadStarted() { base::CommandLine* command_line = base::CommandLine::ForCurrentProcess(); -#if defined(USE_NSS_CERTS) +#if !defined(USE_OPENSSL) // Note: Copied from chrome_render_process_observer.cc to fix b/8676652. // // On platforms where the system NSS shared libraries are used, -- 2.11.4.GIT