Use utilities from build directory instead of own copies

DEPS

 use_relative_paths = True
 
 vars = {
   'chromium_git': 'https://chromium.googlesource.com',
   'pdfium_git': 'https://pdfium.googlesource.com',
 
   'build_revision': '28e8fda8744c8c44bac72eee610642798daf2705',
   'buildtools_revision': '5378d73123b64907773cc5c1bb027b2f765ff00a',
   'clang_revision': 'b6f620b311665e2d96d0921833f54295b9bbf925',
   'cygwin_revision': 'c89e446b273697fadf3a10ff1007a97c0b7de6df',
@@ skipping 151 matching lines @@
   },
   {
     # Pull clang if needed or requested via GYP_DEFINES.
     'name': 'clang',
     'pattern': '.',
     'action': ['python',
                'pdfium/tools/clang/scripts/update.py',
                '--if-needed'
     ],
   },
-  {

[Lei Zhang, 2016/04/29 18:34:52]

If we remove this block, then where does the VS toolchain update happen?

[Wei Li, 2016/04/29 18:47:36]

Should be synced along with the whole build dir based on revision in this file

[Lei Zhang, 2016/04/29 21:22:02]

So I see build/vs_toolchain.py exists and it gets updated when build/ gets
updates. What about the actual VS toolchain that vs_tollchain.py is suppose to
update? Wasn't running this hook what gets us the VS toolchain? Or am I missing
something?

[Wei Li, 2016/04/30 00:03:38]

oops, missed my morning coffee. Fixed.

-    # Update the Windows toolchain if necessary.
-    'name': 'win_toolchain',
-    'pattern': '.',
-    'action': ['python', 'pdfium/build_gyp/vs_toolchain.py', 'update'],
-  },
 ]