summaryrefslogtreecommitdiffstats
path: root/tools/linux/dump-static-initializers.py
diff options
context:
space:
mode:
authorerg@chromium.org <erg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-10-07 00:56:55 +0000
committererg@chromium.org <erg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-10-07 00:56:55 +0000
commit3a89d5d45b37859fee693cbde2f4db8a4b1c80c4 (patch)
tree6e7e2db39332761c5fb8e3e0875de9e1fce0c73c /tools/linux/dump-static-initializers.py
parent14dcf3dfb93ad44cfbaf70ef8d0ecd86c3739d82 (diff)
downloadchromium_src-3a89d5d45b37859fee693cbde2f4db8a4b1c80c4.zip
chromium_src-3a89d5d45b37859fee693cbde2f4db8a4b1c80c4.tar.gz
chromium_src-3a89d5d45b37859fee693cbde2f4db8a4b1c80c4.tar.bz2
profile: Add a way for each ProfileKeyedServiceFactory to specify its user prefernces.
To allow us to compile individual features in/out of a chrome build, we need to attack browser_prefs.cc, which is a giant static registration. This used to be done through another big code path starting in ProfileImpl which call browser::RegisterUserPrefs() which linked to other static methods. Now this is done through overridding ProfileKeyedServiceFactory::RegisterUserPrefs(), and there are no additional dependencies. BUG=none TEST=none Review URL: http://codereview.chromium.org/7901027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104412 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/linux/dump-static-initializers.py')
0 files changed, 0 insertions, 0 deletions