fixup! Composite frame to native surface directly on main thread.(impl part, optional)
authorYongGeol Jung <yg48.jung@samsung.com>
Mon, 15 Jun 2015 11:05:34 +0000 (20:05 +0900)
committerYoungsoo Choi <kenshin.choi@samsung.com>
Tue, 10 Jul 2018 06:57:09 +0000 (06:57 +0000)
commit697d8af3e16ad757102e27e09536928db295a08e
treee69d4850acbeee7372c9ccb4d011ec8fd49211d8
parenta87ffbd9b5ff3dbf728abe3d99f0eb81546325cd
fixup! Composite frame to native surface directly on main thread.(impl part, optional)

We avoid using content::GpuDataManagerImpl::GetInstance() in ui
If we try to build chromium with shared component, this won't work. We
would need to add a gyp dependency on content_browser ui:compositor. But
that would result in a cyclic dependency. So, the only way is to have
ui:compositor not depend on content_browser, and therefore, not using
content::GpuDataManagerImpl

Reviewed by: KwangHyuk Kim, Prashant Nevase, SeungSeop Park
Bug: http://107.108.218.239/bugzilla/show_bug.cgi?id=13303
Change-Id: Ief76bcfebfb4350dbb965aad3997c82a1017b11f
Signed-off-by: YongGeol Jung <yg48.jung@samsung.com>
tizen_src/chromium_impl/content/browser/renderer_host/render_widget_host_view_efl.cc
tizen_src/chromium_impl/ui/gl/gl_shared_context_efl.cc