--
Use Finch to compare the performances of CLD1 and CLD2
Add a compile time constant CLD_VERSION, which indicates the version of CLD. If this is not define, Finch test to compare CLD1 and CLD2 is supposed to be used.
By this CL, each platform will have the below status:
Linux: Use both CLD1 and CLD2 (and use Finch).
Mac OS X: Use both CLD1 and CLD2 (and use Finch).
Windows: Use only CLD1 once because now CLD2 can't be compiled on Windows. After we can have CLD2 compiled on Windows, we will use CLD2 and Finch asap.
iOS: Still use only CLD1. (It's because it is hard to use both CLD1 and CLD2 on mobile platform because of the binary size impact.)
Android: Still use only CLD1. (The same reason as iOS)
So some platforms will have two CLD binaries, but this is temporal in the sense that we intend to use Finch only for Dev and Beta channel. Before releasing the stable Chromium version, we decide which version of CLD is adopted, make another CL to use only one CLD, and send a merge request. (Of course, we hope we will be able to adopt CLD2.)
BUG=240647
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=221380
Review URL: https://chromiumcodereview.appspot.com/22867032
git-svn-id: http://src.chromium.org/svn/trunk/src/build@221675 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
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.