GYP build for ARM untrusted runtime.

build/common.gypi

 # Copyright (c) 2011 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.
 
 {
   'variables': {
     # .gyp files should set chromium_code to 1 if they build Chromium-specific
     # code, as opposed to external code.  This variable is used to control
     # such things as the set of warnings to enable, and whether warnings are
     # treated as errors.
@@ skipping 280 matching lines @@
           [ 'target_arch=="arm"', {
               'cflags': [
                 '-Wno-abi',
                 '-march=armv7-a',
                 '-mtune=cortex-a8',
                 '-mfpu=neon',
                 '-mfloat-abi=softfp',
                 '-fno-exceptions',
                 '-Wall',
                 '-fPIC',
-              ],
-              'cflags_cc': [

[Mark Seaborn, 2012/03/28 07:21:02]

I would still prefer if you did trusted-code Gyp changes in a separate changeset
for clarity.

[Nikolay, 2012/03/28 13:24:23]

OK, will make it separate CL, see
https://chromiumcodereview.appspot.com/9875016/.
On 2012/03/28 07:21:02, Mark Seaborn wrote:

                 '--sysroot=<(sysroot)',
               ],
               'ldflags': [
                 '--sysroot=<(sysroot)',
               ],
             }, { # else: target_arch != "arm"
               'conditions': [
                 ['target_arch=="x64"', {
                   'variables': {
                     'mbits_flag': '-m64',
@@ skipping 486 matching lines @@
     # 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',
   },
   'includes': [
     'untrusted.gypi',
   ],
 }