Roll src/third_party/boringssl/src d7421ebf6..3ac32b1ed

third_party/boringssl/boringssl.gyp

 # Copyright 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.
 
 {
   'targets': [
     {
       'target_name': 'boringssl',
       'type': '<(component)',
       'includes': [
         'boringssl.gypi',
       ],
       'sources': [
         '<@(boringssl_crypto_sources)',
         '<@(boringssl_ssl_sources)',
       ],
       'defines': [
         'BORINGSSL_IMPLEMENTATION',
         'BORINGSSL_NO_STATIC_INITIALIZER',
-        'OPENSSL_SMALL',
       ],
       # TODO(davidben): Fix size_t truncations in BoringSSL.
       # https://crbug.com/429039
       'msvs_disabled_warnings': [ 4267, ],
       'conditions': [
         ['component == "shared_library"', {
           'defines': [
             'BORINGSSL_SHARED_LIBRARY',
           ],
         }],
@@ skipping 64 matching lines @@
           ]
         }],
         ['msan == 1 or (target_arch != "arm" and target_arch != "ia32" and target_arch != "x64" and target_arch != "arm64")', {
           'defines': [ 'OPENSSL_NO_ASM' ],
         }],
       ],
       'include_dirs': [
         'src/include',
       ],
       'direct_dependent_settings': {
+        'defines': [
+          'OPENSSL_SMALL',

[davidben, 2015/11/19 00:16:19]

This is purely for the tests because ED25519 functions are missing, which I feel
kind of silly about. I like that most of our build toggles don't actually affect
the public API.

Thoughts? Another option is we teach generate_build_files.py that certain
outputs are OPENSSL_SMALL, or add a --small flag.

+        ],
         'include_dirs': [
           'src/include',
         ],
         'conditions': [
           ['component == "shared_library"', {
             'defines': [
               'BORINGSSL_SHARED_LIBRARY',
             ],
           }],
         ],
       },
     },
   ],
 }