Implementation of GCAPI reactivation.

chrome/installer/gcapi/gcapi_test.cc

Index: chrome/installer/gcapi/gcapi_test.cc
diff --git a/chrome/installer/gcapi/gcapi_test.cc b/chrome/installer/gcapi/gcapi_test.cc
index 2100744160cfd81160f8a00d18e0cc854141c3e5..b7f08bb1c74e7ce21d814c13609ffb0c21281359 100644
--- a/chrome/installer/gcapi/gcapi_test.cc
+++ b/chrome/installer/gcapi/gcapi_test.cc
@@ -4,6 +4,7 @@
 
 #include <stdio.h>
 
+#include "base/command_line.h"
 #include "chrome/installer/gcapi/gcapi.h"
 #include "testing/gtest/include/gtest/gtest.h"
 
@@ -54,11 +55,17 @@ void call_dynamically() {
   FreeLibrary(module);
 }
 
+const char kManualLaunchTests[] = "launch-chrome";
+
 int main(int argc, char* argv[]) {
+  CommandLine::Init(argc, argv);
+
   testing::InitGoogleTest(&argc, argv);
   RUN_ALL_TESTS();
 
-  call_dynamically();
-  call_statically();
-  printf("LaunchChrome returned %d.\n", LaunchGoogleChrome());
+  if (CommandLine::ForCurrentProcess()->HasSwitch(kManualLaunchTests)) {
+    call_dynamically();
+    call_statically();
+    printf("LaunchChrome returned %d.\n", LaunchGoogleChrome());
+  }

[Roger Tawa OOO till Jul 10th, 2012/01/29 16:32:42]

what's this check for?

[robertshield, 2012/01/30 02:40:39]

Before I started messing around in gcapi, the tests weren't gtests, but rather
an exe that calls a couple of the dll exports, presumably to see whether they
appear to do something or crash. This had the annoying side effect of spawning
top level Chrome windows whenever the tests were run.

I haven't deleted this old behaviour since I believe Mike may still use it, but
i have hidden it behind a flag that I can tell him about if he comes asking. 

 }