Clone of https://chromium.googlesource.com/chromium/src/build with Mozilla's local modifications
99442ed8df
* Handle trailing dots in LastTwoLabels() as in http://codereview.chromium.org/7518035/ . Rename this function to LastTwoComponents() to match the terminology used in the RegistryControlledDomainService and elsewhere in Chrome. * Since callers are using std::string anyway, make the functions in the header take const std::string& instead of char*. This also allows doing string operations on them. * Use string operations (like find_last_of()) in place of hand-written algorithms, for brevity, clarity, and safety. * Avoid "unsigned", which the style guide forbids, and use allowed types like size_t, uint32, or int (depending on the situation). * Avoid #define and "using". * Use standard algorithms for similar reasons as using string ops. * Use file_util functions to significantly abbreviate file reading/writing code. * Use wmain() (on Windows) in combination with FilePath to avoid issues if the provided pathname has extended characters that don't flatten losslessly to the default codepage (thanks Darin for pointing out this issue). * Avoid casting where possible. Avoid some casts for printf()-style calls by using a string stream, which also allows for slightly less boilerplate. * Convert non-error uses of stderr to the chrome-standard VLOG(1). * Correctly handle hostnames with trailing dots in the input file. * In general, shorten code where possible. Because this adds a dependency on base, and ssl_false_start_blacklist_process has the "#host" specifier in net.gyp, bradnelson tells me that base and its dependencies need an explicit "host, target" toolchain list for the Linux builds to work correctly. It would be nice if we could avoid this but I guess gyp would have to be smarter or something. BUG=none TEST=none Review URL: http://codereview.chromium.org/7550002 git-svn-id: http://src.chromium.org/svn/trunk/src/build@95907 4ff67af0-8c30-449e-8e8b-ad334ec8d88c |
||
---|---|---|
internal | ||
linux | ||
mac | ||
temp_gyp | ||
util | ||
win | ||
README.chromium | ||
all.gyp | ||
apply_locales.py | ||
branding_value.sh | ||
build_config.h | ||
common.croc | ||
common.gypi | ||
compiler_version.py | ||
dir_exists.py | ||
download_nacl_irt.py | ||
extract_from_cab.py | ||
grit_action.gypi | ||
grit_target.gypi | ||
gyp_chromium | ||
install-build-deps.sh | ||
install-chroot.sh | ||
output_dll_copy.rules | ||
release.gypi | ||
sanitize-mac-build-log.sed | ||
sanitize-mac-build-log.sh | ||
sanitize-win-build-log.sed | ||
sanitize-win-build-log.sh | ||
whitespace_file.txt |
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.