summaryrefslogtreecommitdiffstats
path: root/chrome
diff options
context:
space:
mode:
authorjoi@chromium.org <joi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-01-16 11:45:17 +0000
committerjoi@chromium.org <joi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-01-16 11:45:17 +0000
commit9061bee8add0e744e50811f7feb77333622775e3 (patch)
tree84571937825706f13b75f1bf3c2967d969129a55 /chrome
parent439589d72750b5e22a339834d7ed4a30c7166b58 (diff)
downloadchromium_src-9061bee8add0e744e50811f7feb77333622775e3.zip
chromium_src-9061bee8add0e744e50811f7feb77333622775e3.tar.gz
chromium_src-9061bee8add0e744e50811f7feb77333622775e3.tar.bz2
Use PCH by default in VS 2010.
According to my testing, VS 2010 does not have problem (b) documented at http://code.google.com/p/chromium/wiki/WindowsPrecompiledHeaders, i.e. it rebuilds the PCH file when necessary because of e.g. preprocessor flag changes. Since we aren't using VS 2010 for official builds, if problem (a) (out of memory) is encountered with VS 2010 when we make the switch to using it for official builds, we can simply turn PCH off explicitly in the include.gypi for the official bots. This change has no effect on VS 2008 bots or users. BUG=110001 Review URL: http://codereview.chromium.org/9139059 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@117845 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome')
0 files changed, 0 insertions, 0 deletions