include boringssl headers from third_party explicitly

chrome/browser/DEPS

 include_rules = [
   "+apps",
   "+ash",
   "+chrome/app",
   "+chrome/chrome_watcher",
   "+chrome/grit",
   "+chrome/install_static",
   "+chrome/installer",
   "+chrome_elf/blacklist",
   "+chrome_elf/chrome_elf_constants.h",
@@ skipping 29 matching lines @@
   "+services/ui/public",
   "+ppapi/c",  # For various types.
   "+ppapi/host",
   "+ppapi/proxy",
   "+ppapi/shared_impl",
   "+rlz",
   "+sandbox/win/src",  # The path doesn't say it, but this is the Windows sandbox.
   "+services/service_manager",
   "+skia/ext",
   "+syzygy/kasko",
+  "+third_party/boringssl/src/include",
   "+third_party/crashpad",
   "+third_party/cros_system_api",
   "+third_party/kasko",
 
   # chrome only needs switches from cc. All usage of the compositor is from
   # content. Definitely don't include generic stuff from cc/base here, if this
   # is needed these files need to move to base/
   "+cc/base/switches.h",
 
   # Unsafe to use from //chrome, see http://goo.gl/QQG5wo
@@ skipping 50 matching lines @@
   "+third_party/WebKit/public/web/WebWindowFeatures.h",
 ]
 
 specific_include_rules = {
   # Exploits don't abide by DEPS; so all IPC message definitions are fair game
   # in this type of test.
   'chrome_security_exploit_browsertest\.cc' : [
     '+content/common',
   ],
 }