chromium-src-build/common.gypi

507 строки
19 KiB
Plaintext
Исходник Обычный вид История

# Copyright (c) 2009 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.
'chromium_code%': 0,
# Variables expected to be overriden on the GYP command line (-D) or by
# ~/.gyp/include.gypi.
# Override chromium_mac_pch and set it to 0 to suppress the use of
# precompiled headers on the Mac. Prefix header injection may still be
# used, but prefix headers will not be precompiled. This is useful when
# using distcc to distribute a build to compile slaves that don't
# share the same compiler executable as the system driving the compilation,
# because precompiled headers rely on pointers into a specific compiler
# executable's image. Setting this to 0 is needed to use an experimental
# Linux-Mac cross compiler distcc farm.
'chromium_mac_pch%': 1,
# Override branding to select the desired branding flavor.
'branding%': 'Chromium',
# Set to 1 to enable code coverage. In addition to build changes
# (e.g. extra CFLAGS), also creates a new target in the src/chrome
# project file called "coverage".
# Currently ignored on Windows.
'coverage%': 0,
# Overridable specification for potential use of alternative
# JavaScript engines.
'javascript_engine%': 'v8',
# To do a shared build on linux we need to be able to choose between type
# static_library and shared_library. We default to doing a static build
# but you can override this with "gyp -Dlibrary=shared_library" or you
# can add the following line (without the #) to ~/.gyp/include.gypi
# {'variables': {'library': 'shared_library'}}
# to compile as shared by default
'library%': 'static_library',
# TODO(bradnelson): eliminate this when possible.
# To allow local gyp files to prevent release.vsprops from being included.
# Yes(1) means include release.vsprops.
# Once all vsprops settings are migrated into gyp, this can go away.
'msvs_use_common_release%': 1,
# The architecture that we're building on.
'target_arch%': 'ia32',
# By default linux does not use views. To turn on views in Linux
# set the variable GYP_DEFINES to "toolkit_views=1", or modify
# ~/.gyp/include.gypi .
'toolkit_views%': 0,
},
'target_defaults': {
'conditions': [
['branding=="Chrome"', {
'defines': ['GOOGLE_CHROME_BUILD'],
'conditions': [
['OS=="linux"', {
'cflags': [ '-gstabs' ],
}],
],
}, { # else: branding!="Chrome"
'defines': ['CHROMIUM_BUILD'],
}],
['toolkit_views==1', {
'defines': ['TOOLKIT_VIEWS=1'],
}],
['coverage!=0', {
'conditions': [
['OS=="mac"', {
'xcode_settings': {
'GCC_INSTRUMENT_PROGRAM_FLOW_ARCS': 'YES',
'GCC_GENERATE_TEST_COVERAGE_FILES': 'YES',
},
# Add -lgcov for executables, not for static_libraries.
# This is a delayed conditional.
'target_conditions': [
['_type=="executable"', {
'xcode_settings': { 'OTHER_LDFLAGS': [ '-lgcov' ] },
}],
],
}],
# Linux gyp (into scons) doesn't like target_conditions?
# TODO(???): track down why 'target_conditions' doesn't work
# on Linux gyp into scons like it does on Mac gyp into xcodeproj.
['OS=="linux"', {
'cflags': [ '-ftest-coverage',
'-fprofile-arcs' ],
'link_settings': { 'libraries': [ '-lgcov' ] },
}],
]},
# TODO(jrg): options for code coverage on Windows
],
],
'default_configuration': 'Debug',
'configurations': {
# VCLinkerTool LinkIncremental values below:
# 0 == default
# 1 == /INCREMENTAL:NO
# 2 == /INCREMENTAL
# Debug links incremental, Release does not.
'Debug': {
'conditions': [
[ 'OS=="mac"', {
'xcode_settings': {
'COPY_PHASE_STRIP': 'NO',
'GCC_OPTIMIZATION_LEVEL': '0',
}
}],
[ 'OS=="win"', {
'configuration_platform': 'Win32',
'msvs_configuration_attributes': {
'OutputDirectory': '$(SolutionDir)$(ConfigurationName)',
'IntermediateDirectory': '$(OutDir)\\obj\\$(ProjectName)',
'CharacterSet': '1',
},
'msvs_settings': {
'VCCLCompilerTool': {
'Optimization': '0',
'PreprocessorDefinitions': ['_DEBUG'],
'BasicRuntimeChecks': '3',
'RuntimeLibrary': '1',
},
'VCLinkerTool': {
'LinkIncremental': '2',
},
'VCResourceCompilerTool': {
'PreprocessorDefinitions': ['_DEBUG'],
},
},
}],
],
},
'Release': {
'defines': [
'NDEBUG',
],
'conditions': [
[ 'OS=="mac"', {
'xcode_settings': {
'DEAD_CODE_STRIPPING': 'YES',
}
}],
[ 'OS=="win" and msvs_use_common_release', {
'configuration_platform': 'Win32',
'msvs_props': ['release.vsprops'],
}],
[ 'OS=="win"', {
'msvs_settings': {
'VCLinkerTool': {
'LinkIncremental': '1',
},
},
}],
],
},
},
},
'conditions': [
['OS=="linux"', {
'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',
},
'cflags': [
'<(werror)', # See note above about the werror variable.
'-pthread',
],
'ldflags': [
'-pthread',
],
'scons_variable_settings': {
'LIBPATH': ['$LIB_DIR'],
# Linking of large files uses lots of RAM, so serialize links
# using the handy flock command from util-linux.
'FLOCK_LINK': ['flock', '$TOP_BUILDDIR/linker.lock', '$LINK'],
'FLOCK_SHLINK': ['flock', '$TOP_BUILDDIR/linker.lock', '$SHLINK'],
'FLOCK_LDMODULE': ['flock', '$TOP_BUILDDIR/linker.lock', '$LDMODULE'],
# We have several cases where archives depend on each other in
# a cyclic fashion. Since the GNU linker does only a single
# pass over the archives we surround the libraries with
# --start-group and --end-group (aka -( and -) ). That causes
# ld to loop over the group until no more undefined symbols
# are found. In an ideal world we would only make groups from
# those libraries which we knew to be in cycles. However,
# that's tough with SCons, so we bodge it by making all the
# archives a group by redefining the linking command here.
#
# TODO: investigate whether we still have cycles that
# require --{start,end}-group. There has been a lot of
# refactoring since this was first coded, which might have
# eliminated the circular dependencies.
#
# Note: $_LIBDIRFLAGS comes before ${LINK,SHLINK,LDMODULE}FLAGS
# so that we prefer our own built libraries (e.g. -lpng) to
# system versions of libraries that pkg-config might turn up.
# TODO(sgk): investigate handling this not by re-ordering the
# flags this way, but by adding a hook to use the SCons
# ParseFlags() option on the output from pkg-config.
'LINKCOM': [['$FLOCK_LINK', '-o', '$TARGET', '$_LIBDIRFLAGS', '$LINKFLAGS', '$SOURCES', '-Wl,--start-group', '$_LIBFLAGS', '-Wl,--end-group']],
'SHLINKCOM': [['$FLOCK_SHLINK', '-o', '$TARGET', '$_LIBDIRFLAGS', '$SHLINKFLAGS', '$SOURCES', '-Wl,--start-group', '$_LIBFLAGS', '-Wl,--end-group']],
'LDMODULECOM': [['$FLOCK_LDMODULE', '-o', '$TARGET', '$_LIBDIRFLAGS', '$LDMODULEFLAGS', '$SOURCES', '-Wl,--start-group', '$_LIBFLAGS', '-Wl,--end-group']],
'IMPLICIT_COMMAND_DEPENDENCIES': 0,
# -rpath is only used when building with shared libraries.
'conditions': [
[ 'library=="shared_library"', {
'RPATH': '$LIB_DIR',
}],
],
},
'scons_import_variables': [
'AS',
'CC',
'CXX',
'LINK',
],
'scons_propagate_variables': [
'AS',
'CC',
'CCACHE_DIR',
'CXX',
'DISTCC_DIR',
'DISTCC_HOSTS',
'HOME',
'INCLUDE_SERVER_ARGS',
'INCLUDE_SERVER_PORT',
'LINK',
'CHROME_BUILD_TYPE',
'CHROMIUM_BUILD',
'OFFICIAL_BUILD',
],
'configurations': {
'Debug': {
'variables': {
'debug_optimize%': '0',
},
'defines': [
'_DEBUG',
],
'cflags': [
'-O<(debug_optimize)',
'-g',
Linux: add Breakpad support This commits a rewrite of the Breakpad Linux client. The old code: * Had a number of plain bugs in it, but those could just have been fixed. * Allocated memory from the heap, which is a no go. * Made libc calls which can enter the dynamic linker - another source of crashes. * Didn't understand some of the tricks needed, like clone() via libc will write to random areas of memory because it assumes that it's only called from libpthread Additionally, we had one more requirement which meant changing the interface: * We need to be able to crash dump the renderers from the browser process. And that last one really needed a rewrite. We intend to try and upstream this new code into Breakpad. The new Breakpad design works like this: When a renderer crashes, a signal handler runs on an alternative stack and collects information about the registers of the thread before the crash. Then we enter Chromium specific code an send a datagram message to a magic file descriptor (4) containing: * the registers and tid of the crashing thread * the active URL * a file descriptor to a socket * a CREDENTIALS structure giving the PID of the renderer. On the other end of the socket is an object on the IO thread (render_crash_handler_host_linux.cc) which reads and parses the datagram. The CREDENTIALS structure is validated by the kernel, so the renderer can't lie about it's PID and try and get the browser to crash dump the wrong process. The browser then ptraces the renderer and extracts all the needed information to write a minidump to a temp file. Then we write a byte to the file descriptor which the renderer gave the browser in the datagram and that's the signal to the renderer to finish dying. It dies by sending itself the same signal which trigger the crash dump in the first place, so it will appear to crash as normal as far as kernel core dumps and waitpid are concerned. The browser then constucts a MIME message in a temp file for upload to the crash service. We then fork out to /usr/bin/wget to actually do the upload (since Debian numbers suggest that 99.8% of users have wget installed.) A second forked child unlinks the temp files once wget has completed. For a browser crash, everything works pretty much the same except that the datagram step is omitted and we clone() off a process to ptrace ourselves and write the minidump. This code is only enabled in Chrome branded builds. Stub source files are substituted in the case of a Chromium build. http://codereview.chromium.org/115526 BUG=9646,10772 TEST=Build a Chrome branded binary. Send SEGV to a renderer and verify that wget output appears on stderr. Send a SEGV to the main binary and verify the same. git-svn-id: http://src.chromium.org/svn/trunk/src/build@16719 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2009-05-22 07:37:45 +04:00
# One can use '-gstabs' to enable building the debugging
# information in STABS format for breakpad's dumpsyms.
],
'ldflags': [
'-rdynamic', # Allows backtrace to resolve symbols.
],
},
'Release': {
'cflags': [
'-O2',
# 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',
],
},
Linux: add Breakpad support This commits a rewrite of the Breakpad Linux client. The old code: * Had a number of plain bugs in it, but those could just have been fixed. * Allocated memory from the heap, which is a no go. * Made libc calls which can enter the dynamic linker - another source of crashes. * Didn't understand some of the tricks needed, like clone() via libc will write to random areas of memory because it assumes that it's only called from libpthread Additionally, we had one more requirement which meant changing the interface: * We need to be able to crash dump the renderers from the browser process. And that last one really needed a rewrite. We intend to try and upstream this new code into Breakpad. The new Breakpad design works like this: When a renderer crashes, a signal handler runs on an alternative stack and collects information about the registers of the thread before the crash. Then we enter Chromium specific code an send a datagram message to a magic file descriptor (4) containing: * the registers and tid of the crashing thread * the active URL * a file descriptor to a socket * a CREDENTIALS structure giving the PID of the renderer. On the other end of the socket is an object on the IO thread (render_crash_handler_host_linux.cc) which reads and parses the datagram. The CREDENTIALS structure is validated by the kernel, so the renderer can't lie about it's PID and try and get the browser to crash dump the wrong process. The browser then ptraces the renderer and extracts all the needed information to write a minidump to a temp file. Then we write a byte to the file descriptor which the renderer gave the browser in the datagram and that's the signal to the renderer to finish dying. It dies by sending itself the same signal which trigger the crash dump in the first place, so it will appear to crash as normal as far as kernel core dumps and waitpid are concerned. The browser then constucts a MIME message in a temp file for upload to the crash service. We then fork out to /usr/bin/wget to actually do the upload (since Debian numbers suggest that 99.8% of users have wget installed.) A second forked child unlinks the temp files once wget has completed. For a browser crash, everything works pretty much the same except that the datagram step is omitted and we clone() off a process to ptrace ourselves and write the minidump. This code is only enabled in Chrome branded builds. Stub source files are substituted in the case of a Chromium build. http://codereview.chromium.org/115526 BUG=9646,10772 TEST=Build a Chrome branded binary. Send SEGV to a renderer and verify that wget output appears on stderr. Send a SEGV to the main binary and verify the same. git-svn-id: http://src.chromium.org/svn/trunk/src/build@16719 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2009-05-22 07:37:45 +04:00
# Some utility binaries need to be build with the host's native
# config (i.e. no 32-bit override).
'Tool': {
'cflags!': ['-m32', '-march=pentium4', '-msse2', '-mfpmath=sse'],
'ldflags!': ['-m32'],
'cflags': [ '-O2' ],
},
},
'variants': {
'coverage': {
'cflags': ['-fprofile-arcs', '-ftest-coverage'],
'ldflags': ['-fprofile-arcs'],
},
'profile': {
'cflags': ['-pg', '-g'],
'ldflags': ['-pg'],
},
'symbols': {
'cflags': ['-g'],
},
},
'conditions': [
[ 'target_arch=="arm"', {
'cflags': [
'-fno-exceptions',
'-Wall',
],
}, { # else: target_arch != "arm"
'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"', {
'cflags': [
'-march=pentium4',
'-msse2',
'-mfpmath=sse',
],
}],
],
'cflags': [
'-m32',
'-fno-exceptions',
'-Wall',
],
'ldflags': [
'-m32',
],
}],
],
},
}],
['OS=="mac"', {
'target_defaults': {
'mac_bundle': 0,
'xcode_settings': {
'ALWAYS_SEARCH_USER_PATHS': 'NO',
'GCC_C_LANGUAGE_STANDARD': 'c99',
'GCC_CW_ASM_SYNTAX': 'NO',
'GCC_ENABLE_PASCAL_STRINGS': 'NO',
'GCC_INLINES_ARE_PRIVATE_EXTERN': 'YES',
'GCC_OBJC_CALL_CXX_CDTORS': 'YES',
'GCC_SYMBOLS_PRIVATE_EXTERN': 'YES',
'GCC_TREAT_WARNINGS_AS_ERRORS': 'YES',
'GCC_VERSION': '4.2',
'GCC_WARN_ABOUT_MISSING_NEWLINE': 'YES',
'MACOSX_DEPLOYMENT_TARGET': '10.5',
'PREBINDING': 'NO',
'SDKROOT': 'macosx10.5',
'USE_HEADERMAP': 'NO',
'WARNING_CFLAGS': ['-Wall', '-Wendif-labels'],
'conditions': [
['chromium_mac_pch', {'GCC_PRECOMPILE_PREFIX_HEADER': 'YES'},
{'GCC_PRECOMPILE_PREFIX_HEADER': 'NO'}],
],
},
'target_conditions': [
['_type!="static_library"', {
'xcode_settings': {'OTHER_LDFLAGS': ['-Wl,-search_paths_first']},
}],
['_mac_bundle', {
'xcode_settings': {'OTHER_LDFLAGS': ['-Wl,-ObjC']},
}],
['_type=="executable"', {
'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)'],
},
],
}],
],
},
}],
['OS=="win"', {
'target_defaults': {
'defines': [
'_WIN32_WINNT=0x0600',
'WINVER=0x0600',
'WIN32',
'_WINDOWS',
'_HAS_EXCEPTIONS=0',
'NOMINMAX',
'_CRT_RAND_S',
'CERT_CHAIN_PARA_HAS_EXTRA_FIELDS',
'WIN32_LEAN_AND_MEAN',
'_SECURE_ATL',
'_HAS_TR1=0',
],
'include_dirs': [
'<(DEPTH)/third_party/platformsdk_win2008_6_1/files/Include',
'$(VSInstallDir)/VC/atlmfc/include',
],
'msvs_cygwin_dirs': ['../third_party/cygwin'],
'msvs_disabled_warnings': [4396, 4503, 4819],
'msvs_settings': {
'VCCLCompilerTool': {
'MinimalRebuild': 'false',
'ExceptionHandling': '0',
'BufferSecurityCheck': 'true',
'EnableFunctionLevelLinking': 'true',
'RuntimeTypeInfo': 'false',
'WarningLevel': '3',
'WarnAsError': 'true',
'DebugInformationFormat': '3',
},
'VCLibrarianTool': {
'AdditionalOptions': '/ignore:4221',
'AdditionalLibraryDirectories':
'<(DEPTH)/third_party/platformsdk_win2008_6_1/files/Lib',
},
'VCLinkerTool': {
'AdditionalOptions':
'/safeseh /dynamicbase /ignore:4199 /ignore:4221 /nxcompat',
'AdditionalDependencies': [
'wininet.lib',
'version.lib',
'msimg32.lib',
'ws2_32.lib',
'usp10.lib',
'psapi.lib',
'dbghelp.lib',
],
'AdditionalLibraryDirectories':
'<(DEPTH)/third_party/platformsdk_win2008_6_1/files/Lib',
'DelayLoadDLLs': 'dbghelp.dll,dwmapi.dll,uxtheme.dll',
'GenerateDebugInformation': 'true',
'MapFileName': '$(OutDir)\\$(TargetName).map',
'ImportLibrary': '$(OutDir)\\lib\\$(TargetName).lib',
'TargetMachine': '1',
'FixedBaseAddress': '1',
# SubSystem values:
# 0 == not set
# 1 == /SUBSYSTEM:CONSOLE
# 2 == /SUBSYSTEM:WINDOWS
# Most of the executables we'll ever create are tests
# and utilities with console output.
'SubSystem': '1',
},
'VCMIDLTool': {
'GenerateStublessProxies': 'true',
'TypeLibraryName': '$(InputName).tlb',
'OutputDirectory': '$(IntDir)',
'HeaderFileName': '$(InputName).h',
'DLLDataFileName': 'dlldata.c',
'InterfaceIdentifierFileName': '$(InputName)_i.c',
'ProxyFileName': '$(InputName)_p.c',
},
'VCResourceCompilerTool': {
'Culture' : '1033',
'AdditionalIncludeDirectories': ['<(DEPTH)'],
},
},
},
}],
['chromium_code==0', {
# This section must follow the other conditon sections above because
# external_code.gypi expects to be merged into those settings.
'includes': [
'external_code.gypi',
],
}],
],
'scons_settings': {
'sconsbuild_dir': '<(DEPTH)/sconsbuild',
},
'xcode_settings': {
# 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',
},
}