Don't use Compositor::Initialize for Aura Android

chrome/browser/chrome_browser_main_android.cc

Index: chrome/browser/chrome_browser_main_android.cc
diff --git a/chrome/browser/chrome_browser_main_android.cc b/chrome/browser/chrome_browser_main_android.cc
index 4fd6d9d710200af8f35ce61a540c1c81723864ef..32b1599265104c65272e9c1920671d630574ff1c 100644
--- a/chrome/browser/chrome_browser_main_android.cc
+++ b/chrome/browser/chrome_browser_main_android.cc
@@ -100,7 +100,9 @@ void ChromeBrowserMainPartsAndroid::PreEarlyInitialization() {
   net::NetworkChangeNotifier::SetFactory(
       new net::NetworkChangeNotifierFactoryAndroid());
 
+#if !defined(USE_AURA)
   content::Compositor::Initialize();

[sky, 2015/11/30 23:56:20]

That this code was compiling tells me you still have the Initialize function. If
you're going to ifdef calling it, shouldn't you also ifdef the function
implementation?
Personally I would be inclined to leave this code as is and have an empty
implementation for android.

[bshe, 2015/12/01 02:24:16]

ifdefed the function declaration.

Sorry. I probably did a bad job explaining this CL. My understanding is that we
will get a compile error for Aura Android without this ifdef. The implementation
for this function is not included in Aura Android. We don't expect to use
Android's compositor. So we use ifdef here instead of implement it for Aura
Android.

+#endif
 
   // Chrome on Android does not use default MessageLoop. It has its own
   // Android specific MessageLoop.