Add missing dependencies.

chrome/chrome_tests_unit.gypi

Index: chrome/chrome_tests_unit.gypi
diff --git a/chrome/chrome_tests_unit.gypi b/chrome/chrome_tests_unit.gypi
index 2a4d83583b5de3149efafe7358f93befa3953b3d..7d89c4f361c022403d361b559835baab1659c791 100644
--- a/chrome/chrome_tests_unit.gypi
+++ b/chrome/chrome_tests_unit.gypi
@@ -2882,6 +2882,7 @@
           'target_name': 'unit_tests_run',
           'type': 'none',
           'dependencies': [
+            '../third_party/mesa/mesa.gyp:osmesa',

[jam, 2015/07/20 22:52:14]

here and in other places, shouldn't this be in unit_tests? that way if someone
has an empty build directory and builds just unit_tests, it should have the
binaries needed.

someone more familiar shoudl review, i couldn't figure out through cs in a quick
search how this is needed for unit tests. i.e. i see for browser tests the code
in
https://code.google.com/p/chromium/codesearch#chromium/src/content/public/tes...
which does this. i ask to know if there's one test target (like test support)
that we can add this to instead of in all these unit tests.

[M-A Ruel, 2015/07/20 23:18:46]

That's a fair question. The main difference is that the tests do not link with
it but I did it anyway since it makes more sense.

[danakj, 2015/07/20 23:56:43]

osmesa is dynamically loaded by GLSurface.

any unit test that uses a full compositor (ie most of our test suites) will use
it via
https://code.google.com/p/chromium/codesearch#chromium/src/ui/gl/gl_surface.c...

browser tests are special cuz they use gpu process not just in process gl.

it'd be nice if they are a dep of the test suite itself, but osmesa is not
linked in, so, does gyp have a way of expressing that?

             'unit_tests',
           ],
           'includes': [