Aura on Android: Compile extensions gn target.

chrome/browser/ui/browser_navigator_params.h

Index: chrome/browser/ui/browser_navigator_params.h
diff --git a/chrome/browser/ui/browser_navigator_params.h b/chrome/browser/ui/browser_navigator_params.h
index d011c0eb986de499fd4bbafe4abd69549d91e2f7..cfc8104bd068e88cb7dcbbd2b08df417dd265daf 100644
--- a/chrome/browser/ui/browser_navigator_params.h
+++ b/chrome/browser/ui/browser_navigator_params.h
@@ -55,7 +55,8 @@ namespace chrome {
 struct NavigateParams {
 #if defined(OS_ANDROID)
   explicit NavigateParams(content::WebContents* a_target_contents);
-#else
+#endif
+#if !defined(OS_ANDROID) || defined(USE_AURA)

[mfomitchev, 2015/11/10 21:27:28]

I don't see any changes to browser_navigator_params.h/cc in auraclank2. Do you
have any idea why we didn't need them in the branch, but we need them now? I
don't see any recent changes in chrome_runtime_api_delegate, which could've
affect this.

[Hadi, 2015/11/12 16:33:36]

I spent some time on this and couldn't figure out why we didn't need this in
auraclank2.

I think somehow chrome_runtime_api_delegate.cc and extension_tab_util.cc don't
get compiled there, but I couldn't figure out what we did it to disable them.

   NavigateParams(Browser* browser,
                  const GURL& a_url,
                  ui::PageTransition a_transition);
@@ -205,7 +206,7 @@ struct NavigateParams {
   // Default is IGNORE.
   RefBehavior ref_behavior;
 
-#if !defined(OS_ANDROID)
+#if !defined(OS_ANDROID) || defined(USE_AURA)
   // [in]  Specifies a Browser object where the navigation could occur or the
   //       tab could be added. Navigate() is not obliged to use this Browser if
   //       it is not compatible with the operation being performed. This can be