Compile remoting client plugin with GN

build/config/crypto.gni

Index: build/config/crypto.gni
diff --git a/build/config/crypto.gni b/build/config/crypto.gni
index 90a45eafee860bfa1d9e3d3f845b0c10f537b535..6461353810db6328ccfb7f7bf420e0ecd2efaec4 100644
--- a/build/config/crypto.gni
+++ b/build/config/crypto.gni
@@ -20,8 +20,10 @@ declare_args() {
 # True when we're using OpenSSL for representing certificates. When targeting
 # Android, the platform certificate library is used for certificate
 # verification. On other targets, this flag also enables OpenSSL for certificate
-# verification, but this configuration is unsupported.
-use_openssl_certs = is_android
+# verification, but this configuration is unsupported. PNaCl remoting plugin
+# doesn't need cert verification but is built with this flag to avoid dependency
+# on NSS.

[davidben, 2015/08/31 23:11:06]

Let's change this to:

True when we're using OpenSSL for representing certificates. When targeting
Android, the platform certificate library is used for certificate verification.
On NaCl, verification isn't supported. Otherwise, OpenSSL is used for
certificate verification, but this configuration is unsupported.

(I think I wrote that comment without realizing the PNaCl target existed.)

I really should just ditch the use_openssl_certs Linux port and disentangle some
of this. We are never going to ship anything based on that code ever. It's grown
organically and is kind of a mess.

[Sergey Ulanov, 2015/09/01 00:06:46]

Done.

+use_openssl_certs = is_android || is_nacl
 
 # True if NSS is used for certificate verification. Note that this is
 # independent from use_openssl. It is possible to use OpenSSL for the crypto