Expose the sandbox related code through the content API. I did a bit of cleanup while I was doing...

chrome/test/pyautolib/pyautolib.h

Index: chrome/test/pyautolib/pyautolib.h
===================================================================
--- chrome/test/pyautolib/pyautolib.h	(revision 107845)
+++ chrome/test/pyautolib/pyautolib.h	(working copy)
@@ -10,11 +10,14 @@
 #pragma once
 
 #include "base/message_loop.h"
-#include "base/mac/scoped_nsautorelease_pool.h"
 #include "base/test/test_timeouts.h"
 #include "chrome/test/ui/ui_test.h"
 #include "chrome/test/ui/ui_test_suite.h"
 
+#if defined(OS_MACOSX)
+#include "base/mac/scoped_nsautorelease_pool.h"
+#endif
+
 // The C++ style guide forbids using default arguments but I'm taking the
 // liberty of allowing it in this file. The sole purpose of this (and the
 // .cc) is to support the python interface, and default args are allowed in
@@ -33,7 +36,9 @@
   void SetCrSourceRoot(const FilePath& path);
 
  private:
+#if defined(OS_MACOSX)
   base::mac::ScopedNSAutoreleasePool pool_;
+#endif
 };
 
 // The primary class that interfaces with Automation Proxy.