clang: Enable using a different compiler path for standalone webkit make builds.

build/common.gypi

Index: build/common.gypi
diff --git a/build/common.gypi b/build/common.gypi
index 9e3fe7ca8127bd6e1270e61c9b1a059a157a0ad4..8047a90de2c95200423f0a1bbf6d0e24fbcdd3b6 100644
--- a/build/common.gypi
+++ b/build/common.gypi
@@ -2544,6 +2544,15 @@
         ['CXX.host', '$(CXX)'],
         ['LINK.host', '$(LINK)'],
       ],
+      'conditions': [
+        ['inside_chromium_build==0', {

[Mark Mentovai, 2011/10/20 13:28:57]

What else sets this variable?

You’re using it to mean “is this a WebKit standalone?” which means that either
you’re not accounting for non-WebKit non-“inside_chromium” builds, or that this
variable is named unfortunately.

What sets inside_chromium_build in a WebKit standalone build? Is that a better
place to set the compiler path?

[Nico, 2011/10/20 14:36:55]

It's named unfortunately, no other build sets it.

http://codesearch.google.com/codesearch#search/&exact_package=chromium&q=insi...
 It's set in third_party/WebKit/Source/WebKit/chromium/gyp_webkit. Setting the
compiler path there is a much better idea. That way the gyp change isn't needed
either. Thanks for the suggestion!

+          'make_global_settings': [
+            # Fix up the paths to work in a stand-alone webkit checkout.
+            ['CC', 'Source/WebKit/chromium/third_party/llvm-build/Release+Asserts/bin/clang'],
+            ['CXX', 'Source/WebKit/chromium/third_party/llvm-build/Release+Asserts/bin/clang++'],
+          ],
+        }],
+      ],
     }],
   ],
   'xcode_settings': {