# 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. 'variables': { # Putting a variables dict inside another variables dict looks kind of # weird. This is done so that 'host_arch', 'chromeos', etc are defined as # variables within the outer variables dict here. This is necessary # to get these variables defined for the conditions within this variables # dict that operate on these variables. 'variables': { 'variables': { 'variables': { 'variables': { # Whether we're building a ChromeOS build. 'chromeos%': 0, # Whether or not we are using the Aura windowing framework. 'use_aura%': 0, # Whether or not we are building the Ash shell. 'use_ash%': 0, # Use a raw surface abstraction. 'use_ozone%': 0, }, # Copy conditionally-set variables out one scope. 'chromeos%': '<(chromeos)', 'use_aura%': '<(use_aura)', 'use_ash%': '<(use_ash)', 'use_ozone%': '<(use_ozone)', # Whether we are using Views Toolkit 'toolkit_views%': 0, # Use OpenSSL instead of NSS. Under development: see http://crbug.com/62803 'use_openssl%': 0, # Disable viewport meta tag by default. 'enable_viewport%': 0, # Enable HiDPI support. 'enable_hidpi%': 0, # Enable touch optimized art assets and metrics. 'enable_touch_ui%': 0, # Override buildtype to select the desired build flavor. # Dev - everyday build for development/testing # Official - release build (generally implies additional processing) # TODO(mmoss) Once 'buildtype' is fully supported (e.g. Windows gyp # conversion is done), some of the things which are now controlled by # 'branding', such as symbol generation, will need to be refactored # based on 'buildtype' (i.e. we don't care about saving symbols for # non-Official # builds). 'buildtype%': 'Dev', # Override branding to select the desired branding flavor. 'branding%': 'Chromium', 'conditions': [ # ChromeOS implies ash. ['chromeos==1', { 'use_ash%': 1, 'use_aura%': 1, }], # For now, Windows builds that |use_aura| should also imply using # ash. This rule should be removed for the future when Windows is # using the aura windows without the ash interface. ['use_aura==1 and OS=="win"', { 'use_ash%': 1, }], ['use_ash==1', { 'use_aura%': 1, }], # Compute the architecture that we're building on. ['OS=="win" or OS=="mac" or OS=="ios"', { '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%': '. Additional # documentation on these macros is available at # http://developer.apple.com/mac/library/technotes/tn2002/tn2064.html#SECTION3 # Chrome normally builds with the Mac OS X 10.6 SDK and sets the # deployment target to 10.6. Other projects, such as O3D, may # override these defaults. # Normally, mac_sdk_min is used to find an SDK that Xcode knows # about that is at least the specified version. In official builds, # the SDK must match mac_sdk_min exactly. If the SDK is installed # someplace that Xcode doesn't know about, set mac_sdk_path to the # path to the SDK; when set to a non-empty string, SDK detection # based on mac_sdk_min will be bypassed entirely. 'mac_sdk_min%': '10.6', 'mac_sdk_path%': '', 'mac_deployment_target%': '10.6', }, 'mac_sdk_min': '<(mac_sdk_min)', 'mac_sdk_path': '<(mac_sdk_path)', 'mac_deployment_target': '<(mac_deployment_target)', # Compile in Breakpad support by default so that it can be # tested, even if it is not enabled by default at runtime. 'mac_breakpad_compiled_in%': 1, 'conditions': [ # mac_product_name is set to the name of the .app bundle as it should # appear on disk. This duplicates data from # chrome/app/theme/chromium/BRANDING and # chrome/app/theme/google_chrome/BRANDING, but is necessary to get # these names into the build system. ['branding=="Chrome"', { 'mac_product_name%': 'Google Chrome', }, { # else: branding!="Chrome" 'mac_product_name%': 'Chromium', }], ['branding=="Chrome" and buildtype=="Official"', { 'mac_sdk%': ', where # typically changes with each launch. This in turn # means that breakpoints in Chrome.dll don't stick from one launch # to the next. For this reason, we turn ASLR off in debug builds. # Note that this is a three-way bool, where 0 means to pick up # the default setting, 1 is off and 2 is on. 'RandomizedBaseAddress': 1, }, 'VCResourceCompilerTool': { 'PreprocessorDefinitions': ['_DEBUG'], }, }, 'conditions': [ ['OS=="linux" or OS=="android"', { 'target_conditions': [ ['_toolset=="target"', { 'cflags': [ '<@(debug_extra_cflags)', ], }], ], }], # Disabled on iOS because it was causing a crash on startup. # TODO(michelea): investigate, create a reduced test and possibly # submit a radar. ['release_valgrind_build==0 and OS!="ios"', { 'xcode_settings': { 'OTHER_CFLAGS': [ '-fstack-protector-all', # Implies -fstack-protector ], }, }], ], }, 'Release_Base': { 'abstract': 1, 'defines': [ 'NDEBUG', ], 'xcode_settings': { 'DEAD_CODE_STRIPPING': 'YES', # -Wl,-dead_strip 'GCC_OPTIMIZATION_LEVEL': '<(mac_release_optimization)', 'OTHER_CFLAGS': [ '<@(release_extra_cflags)', ], }, 'msvs_settings': { 'VCCLCompilerTool': { 'RuntimeLibrary': '<(win_release_RuntimeLibrary)', 'conditions': [ # In official builds, each target will self-select # an optimization level. ['buildtype!="Official"', { 'Optimization': '<(win_release_Optimization)', }, ], # According to MSVS, InlineFunctionExpansion=0 means # "default inlining", not "/Ob0". # Thus, we have to handle InlineFunctionExpansion==0 separately. ['win_release_InlineFunctionExpansion==0', { 'AdditionalOptions': ['/Ob0'], }], ['win_release_InlineFunctionExpansion!=""', { 'InlineFunctionExpansion': '<(win_release_InlineFunctionExpansion)', }], # if win_release_OmitFramePointers is blank, leave as default ['win_release_OmitFramePointers==1', { 'OmitFramePointers': 'true', }], ['win_release_OmitFramePointers==0', { 'OmitFramePointers': 'false', # The above is not sufficient (http://crbug.com/106711): it # simply eliminates an explicit "/Oy", but both /O2 and /Ox # perform FPO regardless, so we must explicitly disable. # We still want the false setting above to avoid having # "/Oy /Oy-" and warnings about overriding. 'AdditionalOptions': ['/Oy-'], }], ], 'AdditionalOptions': [ '<@(win_release_extra_cflags)', ], }, 'VCLinkerTool': { # LinkIncremental is a tri-state boolean, where 0 means default # (i.e., inherit from parent solution), 1 means false, and # 2 means true. 'LinkIncremental': '1', # This corresponds to the /PROFILE flag which ensures the PDB # file contains FIXUP information (growing the PDB file by about # 5%) but does not otherwise alter the output binary. This # information is used by the Syzygy optimization tool when # decomposing the release image. 'Profile': 'true', }, }, 'conditions': [ ['msvs_use_common_release', { 'includes': ['release.gypi'], }], ['release_valgrind_build==0 and tsan==0', { 'defines': [ 'NVALGRIND', 'DYNAMIC_ANNOTATIONS_ENABLED=0', ], }, { 'defines': [ 'DYNAMIC_ANNOTATIONS_ENABLED=1', 'WTF_USE_DYNAMIC_ANNOTATIONS=1', ], }], ['win_use_allocator_shim==0', { 'defines': ['NO_TCMALLOC'], }], ['os_posix==1 and chromium_code==1', { # Non-chromium code is not guaranteed to compile cleanly # with _FORTIFY_SOURCE. Also, fortified build may fail # when optimizations are disabled, so only do that for Release # build. 'defines': [ '_FORTIFY_SOURCE=2', ], }], ['OS=="linux" or OS=="android"', { 'target_conditions': [ ['_toolset=="target"', { 'cflags': [ '<@(release_extra_cflags)', ], }], ], }], ['OS=="ios"', { 'defines': [ 'NS_BLOCK_ASSERTIONS=1', ], }], ], }, # # Concrete configurations # 'Debug': { 'inherit_from': ['Common_Base', 'x86_Base', 'Debug_Base'], }, 'Release': { 'inherit_from': ['Common_Base', 'x86_Base', 'Release_Base'], }, 'conditions': [ [ 'OS=="win"', { # TODO(bradnelson): add a gyp mechanism to make this more graceful. 'Debug_x64': { 'inherit_from': ['Common_Base', 'x64_Base', 'Debug_Base'], }, 'Release_x64': { 'inherit_from': ['Common_Base', 'x64_Base', 'Release_Base'], }, }], ], }, }, 'conditions': [ ['os_posix==1', { 'target_defaults': { 'ldflags': [ '-Wl,-z,now', '-Wl,-z,relro', ], }, }], ['os_posix==1 and chromeos==0', { # Chrome OS enables -fstack-protector-strong via its build wrapper, # and we want to avoid overriding this, so stack-protector is only # enabled when not building on Chrome OS. # TODO(phajdan.jr): Use -fstack-protector-strong when our gcc # supports it. 'target_defaults': { 'cflags': [ '-fstack-protector', '--param=ssp-buffer-size=4', ], }, }], ['os_posix==1 and OS!="mac" and OS!="ios"', { 'target_defaults': { # Enable -Werror by default, but put it in a variable so it can # be disabled in ~/.gyp/include.gypi on the valgrind builders. 'variables': { 'werror%': '-Werror', 'libraries_for_target%': '', }, 'defines': [ '_FILE_OFFSET_BITS=64', ], 'cflags': [ '<(werror)', # See note above about the werror variable. '-pthread', '-fno-exceptions', '-fno-strict-aliasing', # See http://crbug.com/32204 '-Wall', # TODO(evan): turn this back on once all the builds work. # '-Wextra', # Don't warn about unused function params. We use those everywhere. '-Wno-unused-parameter', # Don't warn about the "struct foo f = {0};" initialization pattern. '-Wno-missing-field-initializers', # Don't export any symbols (for example, to plugins we dlopen()). # Note: this is *required* to make some plugins work. '-fvisibility=hidden', '-pipe', ], 'cflags_cc': [ '-fno-rtti', '-fno-threadsafe-statics', # Make inline functions have hidden visiblity by default. # Surprisingly, not covered by -fvisibility=hidden. '-fvisibility-inlines-hidden', # GCC turns on -Wsign-compare for C++ under -Wall, but clang doesn't, # so we specify it explicitly. # TODO(fischman): remove this if http://llvm.org/PR10448 obsoletes it. # http://code.google.com/p/chromium/issues/detail?id=90453 '-Wsign-compare', ], 'ldflags': [ '-pthread', '-Wl,-z,noexecstack', ], 'libraries' : [ '<(libraries_for_target)', ], 'configurations': { 'Debug_Base': { 'variables': { 'debug_optimize%': '0', }, 'defines': [ '_DEBUG', ], 'cflags': [ '-O>(debug_optimize)', '-g', ], 'conditions' : [ ['OS=="android"', { # Only link with needed input sections. This is to avoid getting # undefined reference to __cxa_bad_typeid in the CDU library. 'ldflags': [ '-Wl,--gc-sections', ], }], ['OS=="android" and android_full_debug==0', { # Some configurations are copied from Release_Base to reduce # the binary size. 'variables': { 'debug_optimize%': 's', }, 'cflags': [ '-fomit-frame-pointer', '-fdata-sections', '-ffunction-sections', ], 'ldflags': [ '-Wl,-O1', '-Wl,--as-needed', ], }], ['OS=="linux" and target_arch=="ia32"', { 'ldflags': [ '-Wl,--no-as-needed', ], }], ], }, 'Release_Base': { 'variables': { 'release_optimize%': '2', # Binaries become big and gold is unable to perform GC # and remove unused sections for some of test targets # on 32 bit platform. # (This is currently observed only in chromeos valgrind bots) # The following flag is to disable --gc-sections linker # option for these bots. 'no_gc_sections%': 0, # TODO(bradnelson): reexamine how this is done if we change the # expansion of configurations 'release_valgrind_build%': 0, }, 'cflags': [ '-O<(release_optimize)', # Don't emit the GCC version ident directives, they just end up # in the .comment section taking up binary size. '-fno-ident', # Put data and code in their own sections, so that unused symbols # can be removed at link time with --gc-sections. '-fdata-sections', '-ffunction-sections', ], 'ldflags': [ # Specifically tell the linker to perform optimizations. # See http://lwn.net/Articles/192624/ . '-Wl,-O1', '-Wl,--as-needed', ], 'conditions' : [ ['no_gc_sections==0', { 'ldflags': [ '-Wl,--gc-sections', ], }], ['OS=="android"', { 'variables': { 'release_optimize%': 's', }, 'cflags': [ '-fomit-frame-pointer', ], }], ['clang==1', { 'cflags!': [ '-fno-ident', ], }], ['profiling==1', { 'cflags': [ '-fno-omit-frame-pointer', '-g', ], }], # Can be omitted to reduce output size. Does not seem to affect # crash reporting. ['target_arch=="ia32"', { 'cflags': [ '-fno-unwind-tables', '-fno-asynchronous-unwind-tables', ], }], ], }, }, 'variants': { 'coverage': { 'cflags': ['-fprofile-arcs', '-ftest-coverage'], 'ldflags': ['-fprofile-arcs'], }, 'profile': { 'cflags': ['-pg', '-g'], 'ldflags': ['-pg'], }, 'symbols': { 'cflags': ['-g'], }, }, 'conditions': [ ['target_arch=="ia32"', { 'target_conditions': [ ['_toolset=="target"', { 'asflags': [ # Needed so that libs with .s files (e.g. libicudata.a) # are compatible with the general 32-bit-ness. '-32', ], # All floating-point computations on x87 happens in 80-bit # precision. Because the C and C++ language standards allow # the compiler to keep the floating-point values in higher # precision than what's specified in the source and doing so # is more efficient than constantly rounding up to 64-bit or # 32-bit precision as specified in the source, the compiler, # especially in the optimized mode, tries very hard to keep # values in x87 floating-point stack (in 80-bit precision) # as long as possible. This has important side effects, that # the real value used in computation may change depending on # how the compiler did the optimization - that is, the value # kept in 80-bit is different than the value rounded down to # 64-bit or 32-bit. There are possible compiler options to # make this behavior consistent (e.g. -ffloat-store would keep # all floating-values in the memory, thus force them to be # rounded to its original precision) but they have significant # runtime performance penalty. # # -mfpmath=sse -msse2 makes the compiler use SSE instructions # which keep floating-point values in SSE registers in its # native precision (32-bit for single precision, and 64-bit # for double precision values). This means the floating-point # value used during computation does not change depending on # how the compiler optimized the code, since the value is # always kept in its specified precision. 'conditions': [ ['branding=="Chromium" and disable_sse2==0', { 'cflags': [ '-march=pentium4', '-msse2', '-mfpmath=sse', ], }], # ChromeOS targets Pinetrail, which is sse3, but most of the # benefit comes from sse2 so this setting allows ChromeOS # to build on other CPUs. In the future -march=atom would # help but requires a newer compiler. ['chromeos==1 and disable_sse2==0', { 'cflags': [ '-msse2', ], }], # Use gold linker for Android ia32 target. ['OS=="android"', { 'cflags': [ '-fuse-ld=gold', ], 'ldflags': [ '-fuse-ld=gold', ], }], # Install packages have started cropping up with # different headers between the 32-bit and 64-bit # versions, so we have to shadow those differences off # and make sure a 32-bit-on-64-bit build picks up the # right files. # For android build, use NDK headers instead of host headers ['host_arch!="ia32" and OS!="android"', { 'include_dirs+': [ '/usr/include32', ], }], ], # -mmmx allows mmintrin.h to be used for mmx intrinsics. # video playback is mmx and sse2 optimized. 'cflags': [ '-m32', '-mmmx', ], 'ldflags': [ '-m32', ], }], ], }], ['target_arch=="arm"', { 'target_conditions': [ ['_toolset=="target"', { 'cflags_cc': [ # The codesourcery arm-2009q3 toolchain warns at that the ABI # has changed whenever it encounters a varargs function. This # silences those warnings, as they are not helpful and # clutter legitimate warnings. '-Wno-abi', ], 'conditions': [ ['arm_arch!=""', { 'cflags': [ '-march=<(arm_arch)', ], }], ['arm_tune!=""', { 'cflags': [ '-mtune=<(arm_tune)', ], }], ['arm_fpu!=""', { 'cflags': [ '-mfpu=<(arm_fpu)', ], }], ['arm_float_abi!=""', { 'cflags': [ '-mfloat-abi=<(arm_float_abi)', ], }], ['arm_thumb==1', { 'cflags': [ '-mthumb', ] }], ['OS=="android"', { # Most of the following flags are derived from what Android # uses by default when building for arm, reference for which # can be found in the following file in the Android NDK: # toolchains/arm-linux-androideabi-4.4.3/setup.mk 'cflags': [ # The tree-sra optimization (scalar replacement for # aggregates enabling subsequent optimizations) leads to # invalid code generation when using the Android NDK's # compiler (r5-r7). This can be verified using # webkit_unit_tests' WTF.Checked_int8_t test. '-fno-tree-sra', '-fuse-ld=gold', '-Wno-psabi', ], # Android now supports .relro sections properly. # NOTE: While these flags enable the generation of .relro # sections, the generated libraries can still be loaded on # older Android platform versions. 'ldflags': [ '-Wl,-z,relro', '-Wl,-z,now', '-fuse-ld=gold', ], 'conditions': [ ['arm_thumb==1', { 'cflags': [ '-mthumb-interwork' ], }], ['profiling==1', { 'cflags': [ '-marm', # Probably reduntant, but recommend by "perf" docs. '-mapcs-frame', # Seems required by -fno-omit-frame-pointer. ], }], ['clang==1', { 'cflags!': [ # Clang does not support the following options. '-mthumb-interwork', '-finline-limit=64', '-fno-tree-sra', '-fuse-ld=gold', '-Wno-psabi', ], }], ], }], ], }], ], }], ['target_arch=="mipsel"', { 'target_conditions': [ ['_toolset=="target"', { 'conditions': [ ['mips_arch_variant=="mips32r2"', { 'cflags': ['-mips32r2', '-Wa,-mips32r2'], }, { 'cflags': ['-mips32', '-Wa,-mips32'], }], ], 'cflags': [ '-EL', '-mhard-float', ], 'ldflags': [ '-EL', '-Wl,--no-keep-memory' ], 'cflags_cc': [ '-Wno-uninitialized', ], }], ], }], ['linux_fpic==1', { 'cflags': [ '-fPIC', ], 'ldflags': [ '-fPIC', ], }], ['sysroot!=""', { 'target_conditions': [ ['_toolset=="target"', { 'cflags': [ '--sysroot=<(sysroot)', ], 'ldflags': [ '--sysroot=<(sysroot)', '@(change_mach_o_flags_options)', ], }, ], 'conditions': [ ['asan==1', { 'variables': { 'asan_saves_file': 'asan.saves', }, 'xcode_settings': { 'CHROMIUM_STRIP_SAVE_FILE': '<(asan_saves_file)', }, }], ], 'target_conditions': [ ['mac_pie==1 and release_valgrind_build==0', { # Turn on position-independence (ASLR) for executables. When # PIE is on for the Chrome executables, the framework will # also be subject to ASLR. # Don't do this when building for Valgrind, because Valgrind # doesn't understand slide. TODO: Make Valgrind on Mac OS X # understand slide, and get rid of the Valgrind check. 'xcode_settings': { 'OTHER_LDFLAGS': [ '-Wl,-pie', # Position-independent executable (MH_PIE) ], }, }], ], }], ['(_type=="executable" or _type=="shared_library" or \ _type=="loadable_module") and mac_strip!=0', { 'target_conditions': [ ['mac_real_dsym == 1', { # To get a real .dSYM bundle produced by dsymutil, set the # debug information format to dwarf-with-dsym. Since # strip_from_xcode will not be used, set Xcode to do the # stripping as well. 'configurations': { 'Release_Base': { 'xcode_settings': { 'DEBUG_INFORMATION_FORMAT': 'dwarf-with-dsym', 'DEPLOYMENT_POSTPROCESSING': 'YES', 'STRIP_INSTALLED_PRODUCT': 'YES', 'target_conditions': [ ['_type=="shared_library" or _type=="loadable_module"', { # The Xcode default is to strip debugging symbols # only (-S). Local symbols should be stripped as # well, which will be handled by -x. Xcode will # continue to insert -S when stripping even when # additional flags are added with STRIPFLAGS. 'STRIPFLAGS': '-x', }], # _type=="shared_library" or _type=="loadable_module" ['_type=="executable"', { 'conditions': [ ['asan==1', { 'STRIPFLAGS': '-s $(CHROMIUM_STRIP_SAVE_FILE)', }] ], }], # _type=="executable" and asan==1 ], # target_conditions }, # xcode_settings }, # configuration "Release" }, # configurations }, { # mac_real_dsym != 1 # To get a fast fake .dSYM bundle, use a post-build step to # produce the .dSYM and strip the executable. strip_from_xcode # only operates in the Release configuration. 'postbuilds': [ { 'variables': { # Define strip_from_xcode in a variable ending in _path # so that gyp understands it's a path and performs proper # relativization during dict merging. 'strip_from_xcode_path': 'mac/strip_from_xcode', }, 'postbuild_name': 'Strip If Needed', 'action': ['<(strip_from_xcode_path)'], }, ], # postbuilds }], # mac_real_dsym ], # target_conditions }], # (_type=="executable" or _type=="shared_library" or # _type=="loadable_module") and mac_strip!=0 ], # target_conditions }, # target_defaults }], # OS=="mac" ['OS=="ios"', { 'target_defaults': { 'xcode_settings' : { 'GCC_VERSION': 'com.apple.compilers.llvm.clang.1_0', # This next block is mostly common with the 'mac' section above, # but keying off (or setting) 'clang' isn't valid for iOS as it # also seems to mean using the custom build of clang. # TODO(stuartmorgan): switch to c++0x (see TODOs in the clang # section above). 'CLANG_CXX_LANGUAGE_STANDARD': 'gnu++0x', # Don't use -Wc++0x-extensions, which Xcode 4 enables by default # when building with clang. This warning is triggered when the # override keyword is used via the OVERRIDE macro from # base/compiler_specific.h. 'CLANG_WARN_CXX0X_EXTENSIONS': 'NO', # Warn if automatic synthesis is triggered with # the -Wobjc-missing-property-synthesis flag. 'CLANG_WARN_OBJC_MISSING_PROPERTY_SYNTHESIS': 'YES', 'WARNING_CFLAGS': [ '-Wheader-hygiene', # Don't die on dtoa code that uses a char as an array index. # This is required solely for base/third_party/dmg_fp/dtoa.cc. '-Wno-char-subscripts', # Clang spots more unused functions. '-Wno-unused-function', # See comments on this flag higher up in this file. '-Wno-unnamed-type-template-args', # Match OS X clang C++11 warning settings. '-Wno-c++11-narrowing', '-Wno-reserved-user-defined-literal', ], }, 'target_conditions': [ ['_toolset=="host"', { 'xcode_settings': { 'SDKROOT': 'macosx<(mac_sdk)', # -isysroot 'MACOSX_DEPLOYMENT_TARGET': '<(mac_deployment_target)', }, }], ['_toolset=="target"', { 'xcode_settings': { # This section should be for overriding host settings. But, # since we can't negate the iphone deployment target above, we # instead set it here for target only. 'IPHONEOS_DEPLOYMENT_TARGET': '<(ios_deployment_target)', }, }], ['_type=="executable"', { 'configurations': { 'Release_Base': { 'xcode_settings': { 'DEPLOYMENT_POSTPROCESSING': 'YES', 'STRIP_INSTALLED_PRODUCT': 'YES', }, }, 'Debug_Base': { 'xcode_settings': { # Remove dSYM to reduce build time. 'DEBUG_INFORMATION_FORMAT': 'dwarf', }, }, }, 'conditions': [ ['"<(GENERATOR)"=="xcode"', { 'xcode_settings': { # TODO(justincohen): ninja builds don't support signing yet. 'conditions': [ ['chromium_ios_signing', { # iOS SDK wants everything for device signed. 'CODE_SIGN_IDENTITY[sdk=iphoneos*]': 'iPhone Developer', }, { 'CODE_SIGNING_REQUIRED': 'NO', 'CODE_SIGN_IDENTITY[sdk=iphoneos*]': '', }], ], }, }], ['"<(GENERATOR)"=="xcode" and clang!=1', { 'xcode_settings': { # It is necessary to link with the -fobjc-arc flag to use # subscripting on iOS < 6. 'OTHER_LDFLAGS': [ '-fobjc-arc', ], }, }], ['clang==1', { 'target_conditions': [ ['_toolset=="target"', { 'variables': { 'developer_dir': '=48', { 'target_defaults': { 'cflags': [ '-Wno-unused-local-typedefs', ], }, }], ['clang==1', { 'conditions': [ ['OS=="android"', { # Android could use the goma with clang. 'make_global_settings': [ ['CC', '