Preparing for webkit chromium port fork

Downstreamed v8 extension building & webkit_chromium_port flag
1. Downstreamed building webkit/extension/v8/*.cc files, which were built by upstream webcore by mistake. Now glue will build them. 
   I tested that even though webcore still builds them, there are no errors if glue also builds them. 
2. Added webkit_chromium_port variable to build/common.gypi which is turned off by default. Currently, nothing uses it but the chrome port will need it.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=27122

[yaar, 2009-09-24 17:09:35]

Chromium side of the fork. Thanks!

[Mark Mentovai, 2009-09-24 17:13:34]

lgo

http://codereview.chromium.org/220026/diff/1/2
File build/common.gypi (right):

http://codereview.chromium.org/220026/diff/1/2#newcode53
Line 53: # This variable tells WebCore.gyp and JavaScriptCore.gyp whether they
are
This terminology is slightly confusing to me, because I thought that "WebKit
Chromium port" was the flavor of WebKit that we used in Chromium, regardless of
whether it was a standalone version (what you're calling 1 here) or the full
Chromium version.

Is my understanding of the terminology off, or is this a candidate for revision?

[yaar, 2009-09-24 19:27:45]

renamed variable

[Mark Mentovai, 2009-09-24 19:30:13]

LGTM