Aura: Build on the linux desktop, plus add USE_ASH.

build/common.gypi

 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # IMPORTANT:
 # Please don't directly include this file if you are building via gyp_chromium,
 # since gyp_chromium is automatically forcing its inclusion.
 {
   # Variables expected to be overriden on the GYP command line (-D) or by
   # ~/.gyp/include.gypi.
@@ skipping 53 matching lines @@
           [ 'OS=="win" or OS=="mac"', {
             'host_arch%': 'ia32',
           }, {
             # This handles the Unix platforms for which there is some support.
             # Anything else gets passed through, which probably won't work very
             # well; such hosts should pass an explicit target_arch to gyp.
             'host_arch%':
               '<!(uname -m | sed -e "s/i.86/ia32/;s/x86_64/x64/;s/amd64/x64/;s/arm.*/arm/;s/i86pc/ia32/")',
           }],
 
-          # Ash and ChromeOS require Aura.
-          ['(use_ash==1 or chromeos==1) and chromeos_gtk==0', {
+          # Non-GTK Chromeos implies ash.
+          ['chromeos==1', {

[sadrul, 2012/03/02 03:39:24]

Should this have been 'chromeos==1 and chromeos_gtk==0'?

[Elliot Glaysher, 2012/03/02 17:32:39]

According to saintlou, that's redundant.

[Peter Mayo, 2012/03/04 16:17:56]

We need that to support merges for R18 & earlier.  He has forgotten this before.
 Please put this back unless there is some great shift in recent history.

+            'use_ash%': 1,
             'use_aura%': 1,
           }],
 
+          # For now, Windows *AND* Linux builds that |use_aura| should also
+          # imply using ash. This rule should be removed for the future when
+          # both Linux and Windows are using the aura windows without the ash
+          # interface.
+          ['use_aura==1 and ((OS=="linux" and chromeos==0) or OS=="win")', {
+            'use_ash%': 1,
+          }],
+
           # Set default value of toolkit_views based on OS.
           ['OS=="win" or chromeos==1 or chromeos_gtk==1 or use_aura==1', {
             'toolkit_views%': 1,
           }, {
             'toolkit_views%': 0,
           }],
 
           # ChromeOS GTK implies ChromeOS.
           ['chromeos_gtk==1', {
             'chromeos%': 1,
@@ skipping 256 matching lines @@
           'use_titlecase_in_grd_files%': 1,
         }],
 
         # Enable some hacks to support Flapper only on Chrome OS.
         ['chromeos==1', {
           'enable_flapper_hacks%': 1,
         }, {
           'enable_flapper_hacks%': 0,
         }],
 
-        # Enable file manager extension on Chrome OS or Aura.
-        ['chromeos==1 or use_aura==1', {
+        # Enable file manager extension on Chrome OS.
+        ['chromeos==1', {
           'file_manager_extension%': 1,
         }, {
           'file_manager_extension%': 0,
         }],
 
-        # ... except on Windows even with Aura.
-        ['use_aura==1 and OS=="win"', {
-          'file_manager_extension%': 0,
-        }],
-
         ['OS=="android"', {
           'proprietary_codecs%': 1,
           'enable_webrtc%': 0,
         }],
 
         # Use GPU accelerated cross process image transport by default
         # on linux builds with the Aura window manager
         ['use_aura==1 and OS=="linux"', {
           'ui_compositor_image_transport%': 1,
         }, {
@@ skipping 2431 matching lines @@
     # settings in target dicts.  SYMROOT is a special case, because many other
     # Xcode variables depend on it, including variables such as
     # PROJECT_DERIVED_FILE_DIR.  When a source group corresponding to something
     # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the
     # files to appear (when present) in the UI as actual files and not red
     # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR,
     # and therefore SYMROOT, needs to be set at the project level.
     'SYMROOT': '<(DEPTH)/xcodebuild',
   },
 }