libcc and webkit_compositor targets + stubs

Here are gyp targets and stubs for compiling libcc and the webkit_compositor bindings in chromium. Everything is guarded behind the off-by-default use_libcc_for_compositor gyp variable.  I haven't included the actual code here, but there are scripts to sync.  I plan to land + manually sync the code into place until we're ready to flip the gyp switch.

Snapshot from r126652

BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=153354

[jamesr, 2012-08-24 05:58:30]

I think we're ready to go here, Nat!

[nduca, 2012-08-24 20:15:05]

Agreed, this is so cool. LGTM with a minor test comment.

http://codereview.chromium.org/10828381/diff/10001/cc/test/RunAllTests.cpp
File cc/test/RunAllTests.cpp (right):

http://codereview.chromium.org/10828381/diff/10001/cc/test/RunAllTests.cpp#ne...
cc/test/RunAllTests.cpp:41: ::testing::InitGoogleMock(&argc, argv);
Would it make more sense to copy test_suite.cc from one of the other test dirs
and then just put in our webkit_support::setup/teardown customization?

[jamesr, 2012-08-24 20:31:57]

http://codereview.chromium.org/10828381/diff/10001/cc/test/RunAllTests.cpp
File cc/test/RunAllTests.cpp (right):

http://codereview.chromium.org/10828381/diff/10001/cc/test/RunAllTests.cpp#ne...
cc/test/RunAllTests.cpp:41: ::testing::InitGoogleMock(&argc, argv);
On 2012/08/24 20:15:05, nduca wrote:
> Would it make more sense to copy test_suite.cc from one of the other test dirs
> and then just put in our webkit_support::setup/teardown customization?

yeah definitely. will do

[jamesr, 2012-08-24 20:33:49]

And I need to generate proper copyright headers on new files. Whee!