Add BoringSSL GYP files.

third_party/boringssl/boringssl.gyp

+# Copyright (c) 2014 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.
+
+{
+  'includes': [
+    'boringssl_tests.gypi',
+  ],
+  'targets': [
+    {
+      'target_name': 'boringssl',
+      'type': '<(component)',

[Ryan Sleevi, 2014/07/09 00:03:35]

I don't think this can be built as a <(component) for the WIN case, because it
would lack the __declspec(export) and would lack a .def file that sets up the
exports.

For Mac/Linux, you're having to turn off -fvisibility=hidden, so I suspect this
is a real issue?

Building this as a static library seems correct?

Alternatively, it would mean no Windows compile, which may be intentional, but
not long-term.

[agl, 2014/07/09 16:42:00]

I think you're correct. I took this from the existing openssl.gyp. Have switched
to a static_library and removed the -fvisibility=hidden hack. (I would like to
have proper export controls in BoringSSL, but we don't have it yet.)

+      'includes': [
+        'boringssl.gypi',
+      ],
+      'sources': [
+        '<@(boringssl_lib_sources)',
+      ],
+      'conditions': [
+        ['target_arch == "arm"', {
+          'sources': [ '<@(boringssl_linux_arm_sources)' ],
+        }],
+        ['target_arch == "ia32"', {
+          'conditions': [
+            ['OS == "mac"', {
+              'sources': [ '<@(boringssl_mac_x86_sources)' ],
+            }],
+            ['OS == "linux"', {
+              'sources': [ '<@(boringssl_linux_x86_sources)' ],
+            }],
+            ['OS != "mac" and OS != "linux"', {
+              'defines': [ 'OPENSSL_NO_ASM' ],
+            }],
+          ]
+        }],
+        ['target_arch == "x64"', {
+          'conditions': [
+            ['OS == "mac"', {
+              'sources': [ '<@(boringssl_mac_x86_64_sources)' ],
+            }],
+            ['OS == "linux"', {
+              'sources': [ '<@(boringssl_linux_x86_64_sources)' ],
+            }],
+            ['OS == "win"', {
+              'sources': [ '<@(boringssl_win_x86_64_sources)' ],
+            }],
+            ['OS != "mac" and OS != "linux" and OS != "win"', {
+              'defines': [ 'OPENSSL_NO_ASM' ],
+            }],
+          ]
+        }],
+        ['target_arch != "arm" and target_arch != "x86" and target_arch != "x64"', {
+          'defines': [ 'OPENSSL_NO_ASM' ],
+        }],
+        ['component == "shared_library"', {
+          'xcode_settings': {
+            'GCC_SYMBOLS_PRIVATE_EXTERN': 'NO',  # no -fvisibility=hidden
+          },
+          'cflags!': ['-fvisibility=hidden'],
+        }],
+      ],
+      'include_dirs': [
+        'src/include',
+        # This is for arm_arch.h, which is needed by some asm files. Since the
+        # asm files are generated and kept in a different directory, they
+        # cannot use relative paths to find this file.
+        'src/crypto',
+      ],
+      'direct_dependent_settings': {
+        'include_dirs': [
+          'src/include',
+        ],
+      },
+    },
+    {
+      'target_name': 'boringssl_unittests',
+      'type': 'executable',
+      'sources': [
+        'boringssl_unittest.cc',
+       ],
+      'dependencies': [
+        '<@(boringssl_test_targets)',
+        '../../base/base.gyp:base',
+        '../../base/base.gyp:run_all_unittests',
+        '../../base/base.gyp:test_support_base',
+        '../../testing/gtest.gyp:gtest',
+      ],
+    },
+  ],
+}
+
+# Local Variables:
+# tab-width:2
+# indent-tabs-mode:nil
+# End:
+# vim: set expandtab tabstop=2 shiftwidth=2:

[Ryan Sleevi, 2014/07/09 00:03:35]

Our GYP files removed mode-lines. There are utilities in tools to setup
file-type rules, but we don't put them in the GYP bits

[agl, 2014/07/09 16:42:00]

Done (again, taken from openssl.gyp).