Commit d4fb1836 authored by rjkroege@chromium.org's avatar rjkroege@chromium.org

Fix linkage for components_unittest for ozone=1

A build of components_unittest with ozone=1 and chromeos=1 requires
an implementation of PowerSaveBlockerImpl. This change provides
a stub implementation pending ozone power management implementation.

BUG=252412

Review URL: https://chromiumcodereview.appspot.com/17511002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207953 0039d316-1c4b-4281-b951-d872f2087c98
parent e831ec34
// Copyright 2013 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
#include "content/browser/power_save_blocker_impl.h"
#include "base/logging.h"
#include "base/memory/ref_counted.h"
namespace content {
// TODO(rjkroege): Add display power saving control to the ozone interface.
// This implementation is necessary to satisfy linkage.
class PowerSaveBlockerImpl::Delegate
: public base::RefCountedThreadSafe<PowerSaveBlockerImpl::Delegate> {
public:
Delegate() {}
private:
friend class base::RefCountedThreadSafe<Delegate>;
virtual ~Delegate() {}
DISALLOW_COPY_AND_ASSIGN(Delegate);
};
PowerSaveBlockerImpl::PowerSaveBlockerImpl(PowerSaveBlockerType type,
const std::string& reason)
: delegate_(new Delegate()) {
NOTIMPLEMENTED();
}
PowerSaveBlockerImpl::~PowerSaveBlockerImpl() { NOTIMPLEMENTED(); }
} // namespace content
......@@ -697,6 +697,7 @@
'browser/power_save_blocker_impl.cc',
'browser/power_save_blocker_impl.h',
'browser/power_save_blocker_mac.cc',
'browser/power_save_blocker_ozone.cc',
'browser/power_save_blocker_win.cc',
'browser/power_save_blocker_x11.cc',
'browser/ppapi_plugin_process_host.cc',
......@@ -1344,6 +1345,7 @@
],
'sources!': [
'browser/geolocation/wifi_data_provider_linux.cc',
'browser/power_save_blocker_ozone.cc',
'browser/power_save_blocker_x11.cc',
'browser/renderer_host/gtk_key_bindings_handler.cc',
'browser/renderer_host/gtk_key_bindings_handler.h',
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment