Support building BoringSSL with NSS certificates.

crypto/rsa_private_key_nss_unittest.cc

Index: crypto/rsa_private_key_nss_unittest.cc
diff --git a/crypto/rsa_private_key_nss_unittest.cc b/crypto/rsa_private_key_nss_unittest.cc
index 98360e810d7dd9678ec94c34a24ad0231e90af9e..777fd9f20389edf92db7dfcf45114f3f466095a4 100644
--- a/crypto/rsa_private_key_nss_unittest.cc
+++ b/crypto/rsa_private_key_nss_unittest.cc
@@ -13,6 +13,10 @@
 
 namespace crypto {
 
+// TODO(davidben): These tests assume NSS is used for both the internal crypto
+// library and the platform key store.
+#if !defined(USE_NSS)

[davidben, 2015/02/25 21:09:39]

This file is really weird because the APIs in question are problematic. I
eventually opted to put the USE_OPENSSL check in the build file and the USE_NSS
check in the source to be consistent with rsa_private_key_nss.cc.

+
 class RSAPrivateKeyNSSTest : public testing::Test {
  public:
   RSAPrivateKeyNSSTest() {}
@@ -57,4 +61,6 @@ TEST_F(RSAPrivateKeyNSSTest, FailedFindFromPublicKey) {
   EXPECT_EQ(NULL, crypto::RSAPrivateKey::FindFromPublicKeyInfo(public_key));
 }
 
+#endif  // !USE_NSS
+
 }  // namespace crypto