Clone of https://chromium.googlesource.com/chromium/src/build with Mozilla's local modifications
37ddeddd22
The latest google-chrome packages contain a sandbox binary, which the development builds of chromium will pick up on automatically. However, for safety reasons, the sandbox binary will only exec a fixed chrome binary location. Since development builds will be somewhere else in the filesystem, this means that they will fail to start their zygote processes and generally be very sad. However, we /do/ want people developing with the sandbox, but we don't want the general sandbox binary to be able to exec anything. We could have chromium try and find its sandbox binary relative to the build directory, but some people build on NFS and, since the sandbox binary needs to be SUID, this won't work for them. Instead, we add a new target: chrome_devel_sandbox which developers can use. This builds a sandbox binary that will exec anything which is owned by the running user. This alternative sandbox binary can be selected by exporting CHROME_DEVEL_SANDBOX. git-svn-id: http://src.chromium.org/svn/trunk/src/build@20709 4ff67af0-8c30-449e-8e8b-ad334ec8d88c |
||
---|---|---|
internal | ||
linux | ||
mac | ||
temp_gyp | ||
util | ||
win | ||
README.chromium | ||
all.gyp | ||
branding_value.sh | ||
build_config.h | ||
common.croc | ||
common.gypi | ||
common.vsprops | ||
common.xcconfig | ||
debug.vsprops | ||
debug.xcconfig | ||
dynamiclib.xcconfig | ||
executable.xcconfig | ||
external_code.gypi | ||
external_code.vsprops | ||
install-build-deps.sh | ||
output_dll_copy.rules | ||
release.vsprops | ||
release.xcconfig | ||
staticlib.xcconfig |
README.chromium
List of property sheets to be included by projects: common.vsprops Not used anymore. No-op. Kept for compatibility with current projects. debug.vsprops Enables debug settings. Must be included directly in Debug configuration. Includes internal\essential.vsprops. external_code.vsprops Contains settings made to simplify usage of external (non-Google) code. It relaxes the warning levels. Should be included after debug.vsprops or release.vsprops to override their settings. output_dll_copy.rules Run to enable automatic copy of DLL when they are as an input file in a vcproj project. release.vsprops Enables release settings. Must be included directly in Release configuration. Includes internal\essential.vsprops. Also includes "internal\release_impl$(CHROME_BUILD_TYPE).vsprops". So the behavior is dependant on the CHROME_BUILD_TYPE environment variable.