Make GN build work on Mac again.

build/config/BUILD.gn

 # Copyright (c) 2013 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 import("//build/config/crypto.gni")
 import("//build/config/features.gni")
 import("//build/config/ui.gni")
 
 declare_args() {
   # When set, turns off the (normally-on) iterator debugging and related stuff
@@ skipping 86 matching lines @@
     defines += [ "USE_CLIPBOARD_AURAX11=1" ]
   }
   if (use_default_render_theme) {
     defines += [ "USE_DEFAULT_RENDER_THEME=1" ]
   }
   if (use_glib) {
     defines += [ "USE_GLIB=1" ]
   }
   if (use_openssl) {
     defines += [ "USE_OPENSSL=1" ]
-  } else {
+    if (use_openssl_certs) {
+      defines += [ "USE_OPENSSL_CERTS=1" ]
+    }
+  } else if (use_nss_certs) {
+    # USE_NSS really means "use nss for certificate validation and storage"
+    # and not "we're linking to NSS." This should probably be renamed
+    # USE_NSS_CERTS to match OpenSSL and our build flag definitions.

[Ryan Sleevi, 2014/04/18 00:25:07]

No it should not.

OpenSSL having two flags is part of the transition away from NSS. USE_NSS is
going to go away entirely - but this flag is certainly not going to be renamed
before then. There's the distinction so that we could explicitly avoid #ifdef
churn renaming all of USE_OPENSSL / USE_NSS to something different.

     defines += [ "USE_NSS=1" ]
   }
   if (use_ozone) {
     defines += [ "USE_OZONE=1" ]
   }
   if (use_x11) {
     defines += [ "USE_X11=1" ]
     if (use_xi2_mt > 0) {
       defines += [ "USE_XI2_MT=$use_xi2_mt" ]
     }
@@ skipping 94 matching lines @@
       "CoreText.framework",
       "Foundation.framework",
       "UIKit.framework",
     ]
   } else if (is_linux) {
     libs = [
       "dl",
     ]
   }
 }