ui/base: Remove ui_unittests target.

ui/base/ui_base_tests_bundle.gypi

 # 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.
 
-# This file contains resources for the ui_unittests test bundle.
+# This file contains resources for the ui_base_unittests test bundle.
 # See chrome_dll_bundle.gypi for a description of the techniques here.
 {
   'product_name': 'ui_unittests Framework',

[tfarina, 2014/11/23 16:52:39]

Nico, Trent, is it fine to change this name in this CL? I was planning to rename
it in a follow up, as I don't know if it is fine or not. Not sure how it will
effect iOS/Mac build.

[tapted, 2014/11/23 22:12:32]

So long as the string literal in ui/base/test/run_all_unittests.cc is updated at
the same time, nothing comes to mind that might explode.

I'd also consider not renaming it. It doesn't have a dependency on
ui_base_unittests, and lots of test targets that are not "ui_base" use
ui_test.pak. This Framework bundle is just a wrapper around ui_test.pak. If,
say, app_list_unittests wanted a (semi)proper app bundle, it could re-use this.

So, not renaming is probably my preference, but I don't have strong feelings
about it.

[tfarina, 2014/11/24 17:23:44]

Thanks Trent. I will let that for a follow up CL then. 

   'variables': {
     # There is no executable in the mock framework, and so nothing to strip.
     'mac_strip': 0,
   },
   'mac_bundle': 1,
   'xcode_settings': {
     'CHROMIUM_BUNDLE_ID': 'com.google.ChromiumUITests',
     'DYLIB_COMPATIBILITY_VERSION': '1.0.0',
     'DYLIB_CURRENT_VERSION': '1.0.0',
     'DYLIB_INSTALL_NAME_BASE': '@executable_path/../Versions/1.0.0.0',
@@ skipping 27 matching lines @@
       'postbuild_name': 'Symlink chrome_100_percent for test',
       'action': [
         'ln',
         '-fns',
         'ui_test.pak',
         '${BUILT_PRODUCTS_DIR}/${WRAPPER_NAME}/Versions/A/Resources/chrome_100_percent.pak'
       ],
     },
   ],
 }