Speculative fix for mini_installer size increase.

Speculative fix for mini_installer size increase.

At least on Mac and Linux, the linker loads object files from static libraries
by loading a .o file that contains symbols it's missing, then adds symbols
needed by that .o file to the missing symbol list, and then it repeats that
process. Since uninstall.cc uses SupplementaryBranding and calls
ClearProductState, that causes rlz_lib.o to be loaded. That references
symbols in financial_ping.cc, which references net.

In the hope of msvc's linker working the same way, move the symbols used
by uninstall.cc into its own file that doesn't depend on symbols in
financial_ping. That way, the linker hopefully won't pull in net and content
when linking mini_installer.

BUG=chromium:120427
TEST=none

[thakis, 2012-03-27 17:14:02]

Not sure if this will work, but it's worth a try.

https://codereview.appspot.com/5936043/diff/2001/lib/rlz_lib_clear.cc
File lib/rlz_lib_clear.cc (right):

https://codereview.appspot.com/5936043/diff/2001/lib/rlz_lib_clear.cc#newcode39
lib/rlz_lib_clear.cc:39: VERIFY(store->ClearPingTime(product));
Note: I changed this from calling FinancialPing::ClearPingTime() to calling the
store directly.

https://codereview.appspot.com/5936043/diff/2001/lib/rlz_lib_clear.cc#newcode44
lib/rlz_lib_clear.cc:44: VERIFY(store->ClearAccessPointRlz(access_points[i]));
Same here.

[Roger Tawa (Google), 2012-03-27 17:35:57]

lgtm

Another solution to this problem would be to not use the chrome stack for
windows builds of chrome.