blob: 6197887d6faf1bee3563a4fbef76cd0db936de8a [file] [log] [blame]
# Copyright (c) 2011, the Dart project authors. Please see the AUTHORS file
# for details. All rights reserved. Use of this source code is governed by a
# BSD-style license that can be found in the LICENSE file.
'variables': {
# Mac OS X SDK and deployment target support.
# The SDK identifies the version of the system headers that will be used,
# and corresponds to the MAC_OS_X_VERSION_MAX_ALLOWED compile-time macro.
# "Maximum allowed" refers to the operating system version whose APIs are
# available in the headers.
# The deployment target identifies the minimum system version that the
# built products are expected to function on. It corresponds to the
# MAC_OS_X_VERSION_MIN_REQUIRED compile-time macro.
# To ensure these macros are available, #include <AvailabilityMacros.h>.
# Additional documentation on these macros is available at
# Chrome normally builds with the Mac OS X 10.5 SDK and sets the
# deployment target to 10.5. Other projects, such as O3D, may override
# these defaults.
'mac_sdk%': '<!(python <(DEPTH)/tools/gyp/ 10.6)',
'mac_deployment_target%': '10.6',
'xcode_settings': {
# This block adds *project-wide* configuration settings to each project
# file. It's almost always wrong to put things here. Specify your
# custom xcode_settings in target_defaults to add them to targets instead.
# In an Xcode Project Info window, the "Base SDK for All Configurations"
# setting sets the SDK on a project-wide basis. In order to get the
# configured SDK to show properly in the Xcode UI, SDKROOT must be set
# here at the project level.
'SDKROOT': 'macosx<(mac_sdk)', # -isysroot
# The Xcode generator will look for an xcode_settings section at the root
# of each dict and use it to apply settings on a file-wide basis. Most
# settings should not be here, they should be in target-specific
# xcode_settings sections, or better yet, should use non-Xcode-specific
# 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',
# It is here to make it possible to run binaries with shared libraries.
# However, it may create problems if you move the shared library. Also,
# this may not be appropriate for "release release" builds.
# Perhaps we should set it to @rpath instead. See