Reland of Link to DirectWrite directly, instead of calling LoadLibrary

ui/aura/aura.gyp

 # Copyright (c) 2012 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.
 
 {
   'variables': {
     'chromium_code': 1,
   },
   'targets': [
     {
@@ skipping 225 matching lines @@
       ],
       'sources': [
         'demo/demo_main.cc',
       ],
       'conditions': [
         ['use_x11==1', {
           'dependencies': [
             '../gfx/x/gfx_x11.gyp:gfx_x11',
           ],
         }],
+        ['OS=="win"', {

[scottmg, 2016/07/01 19:19:02]

I feel like this should be depending on ui/gfx or whatever uses dwrite, rather
than linking the lib itself?

[Ilya Kulshin, 2016/07/01 19:46:39]

Unless I'm misunderstanding the gyp, it looks like this already has a dependency
on gfx (line 229), which links dwrite.lib. Do we expect our build system to pull
in that dependency to the parent?

+          'msvs_settings': {
+            'VCLinkerTool': {
+              'AdditionalDependencies': [
+                'dwrite.lib',
+              ]
+            }
+          }
+        }],
       ]
     },
     {
       'target_name': 'aura_unittests',
       'type': 'executable',
       'dependencies': [
         '../../base/base.gyp:test_support_base',
         '../../skia/skia.gyp:skia',
         '../../testing/gtest.gyp:gtest',
         '../base/ime/ui_base_ime.gyp:ui_base_ime',
@@ skipping 51 matching lines @@
               'dependencies': [
                 '../../tools/xdisplaycheck/xdisplaycheck.gyp:xdisplaycheck',
               ],
             }],
           ],
         },
       ],
     }],
   ],
 }