diff options
| author | tommi@chromium.org <tommi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-10-21 07:00:22 +0000 |
|---|---|---|
| committer | tommi@chromium.org <tommi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-10-21 07:00:22 +0000 |
| commit | b4966382d5d5b72c2fa1ba76aa045128eaf90418 (patch) | |
| tree | f57004fa72e42181b6e3186528ca331ceb05cfd6 /chrome/chrome_common.gypi | |
| parent | f44d1193f728c17cc4fd7adfe11a3fce82cddb9b (diff) | |
| download | chromium_src-b4966382d5d5b72c2fa1ba76aa045128eaf90418.zip chromium_src-b4966382d5d5b72c2fa1ba76aa045128eaf90418.tar.gz chromium_src-b4966382d5d5b72c2fa1ba76aa045128eaf90418.tar.bz2 | |
Move ScopedCoMem to base/win. This is to allow the class to be used from folders that aren't allowed to depend on chrome/common (and besides, ScopedCoMem belongs in base/win anyway).
I'm also adding a DCHECK to ScopedComInitializer that checks if the construction thread is the same as the destruction thread. The reason for this is that I've noticed cases where an instance is created on the heap (as opposed to the usual stack usecase) which could leave the door open to incorrect COM uninitialization.
Review URL: http://codereview.chromium.org/8354035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106687 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_common.gypi')
| -rw-r--r-- | chrome/chrome_common.gypi | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/chrome/chrome_common.gypi b/chrome/chrome_common.gypi index 51abedf..e67806b 100644 --- a/chrome/chrome_common.gypi +++ b/chrome/chrome_common.gypi @@ -197,7 +197,6 @@ 'common/render_messages.cc', 'common/render_messages.h', 'common/safe_browsing/safebrowsing_messages.h', - 'common/scoped_co_mem.h', 'common/search_provider.h', 'common/service_messages.h', 'common/service_process_util.cc', |