In preparation for becoming an internal plugin in chrome I did these things:...

plugin/win/update_lock.h

 /*
  * Copyright 2009, Google Inc.
  * All rights reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions are
  * met:
  *
  *     * Redistributions of source code must retain the above copyright
  * notice, this list of conditions and the following disclaimer.
@@ skipping 15 matching lines @@
  * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
  * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
  * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
  * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  */
 
 
 #ifndef O3D_PLUGIN_WIN_UPDATE_LOCK_H_
 #define O3D_PLUGIN_WIN_UPDATE_LOCK_H_
 
+#if !defined(O3D_INTERNAL_PLUGIN)
+
 #include <windows.h>
 #include "base/basictypes.h"
 
 namespace update_lock {
 
 const TCHAR kRunningEventName[] =
     L"Global\\{AA4817F6-5DB2-482f-92E9-6BD2FF9F3B14}";
 
 class HandleWrapper {
  public:
@@ skipping 43 matching lines @@
     }
   }
   // An event is used to lock out updates since events are closed by the OS
   // if their process dies.  So, updates can still happen if an O3D executable
   // crashes (as long as all instances of the running event are closed, either
   // properly or due to a crash).
   return CreateEvent(security_attributes, FALSE, FALSE, kRunningEventName);
 }
 }  // namespace update_lock
 
+#endif  // O3D_INTERNAL_PLUGIN
+
 #endif  // O3D_PLUGIN_WIN_UPDATE_LOCK_H_