Provide gtest printers for ui/gfx geometry types

ui/events/events.gyp

 # Copyright 2013 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 256 matching lines @@
     },
     {
       'target_name': 'events_unittests',
       'type': '<(gtest_target_type)',
       'dependencies': [
         '<(DEPTH)/base/base.gyp:base',
         '<(DEPTH)/base/base.gyp:run_all_unittests',
         '<(DEPTH)/base/base.gyp:test_support_base',
         '<(DEPTH)/skia/skia.gyp:skia',
         '<(DEPTH)/testing/gtest.gyp:gtest',
+        '../gfx/gfx.gyp:gfx',

[danakj, 2014/07/07 18:52:27]

why this? does everyone have to include gfx that includes gfx_geometry now?

[jamesr, 2014/07/07 19:37:24]

Everyone that depends on gfx_test_support has to depend on both gfx and
gfx_geometry. Production targets that use only gfx_geometry do not have to
depend on gfx.  This is a test target, so it needs both.

We could also split gfx_test_support up and have a gfx_geometry_test_support to
avoid this, but since it only impacts unit test targets this seemed better to
me.

[danakj, 2014/07/07 19:40:05]

ok, thanks.

I think the goal is to have gfx/geometry more independent from gfx/ in general
so this seems like something worth doing eventually, but it doesn't have to be
now.

         '../gfx/gfx.gyp:gfx_geometry',
         '../gfx/gfx.gyp:gfx_test_support',
         'dom4_keycode_converter',
         'events',
         'events_base',
         'events_test_support',
         'gesture_detection',
         'platform/events_platform.gyp:events_platform',
       ],
       'sources': [
@@ skipping 61 matching lines @@
           ],
           'variables': {
             'test_suite_name': 'events_unittests',
           },
           'includes': [ '../../build/apk_test.gypi' ],
         },
       ],
     }],
   ],
 }