yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kwin/plugins/platforms/virtual/CMakeLists.txt

24 lines
661 B
Text
Raw Normal View History

[wayland] Add a virtual framebuffer backend A new backend which doesn't present the rendered output. It uses a QPainter scene, renders to a QImage but doesn't present it anywhere. Thus a real virtual backend. By exporting the environment variable KWIN_WAYLAND_VIRTUAL_SCREENSHOTS the backend creates a temporary dir, prints the path to std-out and saves each rendered frame into that directory. Of course with exit it will be deleted again.
2015-10-02 08:44:29 +00:00
set(VIRTUAL_SOURCES
[backends/virtual] Add a virtual rendering OpenGLBackend The backend is based on drm's gbm backend and also uses the GBM platform, but with the default display allowing the driver to pick a device. In addition it doesn't use a surface, but a surfaceless context with a framebuffer object to render to. Given that it diverged too much from drm's backend to allow more code sharing. If KWin is started from a tty it gets a proper driver, if KWin is started in a X11 session it only gets llvmpipe. Given that there is a chance that the autotests using the virtual backend will fail. In that case a follow up patch will enforce either O2 or Q.
2015-10-08 14:12:09 +00:00
egl_gbm_backend.cpp
[wayland] Add a virtual framebuffer backend A new backend which doesn't present the rendered output. It uses a QPainter scene, renders to a QImage but doesn't present it anywhere. Thus a real virtual backend. By exporting the environment variable KWIN_WAYLAND_VIRTUAL_SCREENSHOTS the backend creates a temporary dir, prints the path to std-out and saves each rendered frame into that directory. Of course with exit it will be deleted again.
2015-10-02 08:44:29 +00:00
virtual_backend.cpp
scene_qpainter_virtual_backend.cpp
screens_virtual.cpp
)
[platforms/virtual] Use rendernode or vgem device if available for egl Summary: The egl implementation for the virtual platform tries to use a render node if available. If there is no render node it looks for a virtual (kernel driver vgem) device, which unfortunately does not create a render node in mainline kernel (there are patches in ChromiumOS). For this the Udev wrapper is extended to search for renderNode devices and for virtual dri devices. If either render node or vgem dri device is found, it is tried to be opened (without logind escalation) and on success a gbm device is created on it. If any step of this fails the so far default behavior of default device is tried for creating the EGLDisplay. All of this is compile optional, so that the virtual platform does not hard depend on udev and/or gbm. Test Plan: Auto tests which need OpenGL executed and verified that they use the render node or vgem device. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2216
2016-07-19 08:51:09 +00:00
include(ECMQtDeclareLoggingCategory)
ecm_qt_declare_logging_category(VIRTUAL_SOURCES HEADER logging.h IDENTIFIER KWIN_VIRTUAL CATEGORY_NAME kwin_platform_virtual DEFAULT_SEVERITY Critical)
[wayland] Add a virtual framebuffer backend A new backend which doesn't present the rendered output. It uses a QPainter scene, renders to a QImage but doesn't present it anywhere. Thus a real virtual backend. By exporting the environment variable KWIN_WAYLAND_VIRTUAL_SCREENSHOTS the backend creates a temporary dir, prints the path to std-out and saves each rendered frame into that directory. Of course with exit it will be deleted again.
2015-10-02 08:44:29 +00:00
add_library(KWinWaylandVirtualBackend MODULE ${VIRTUAL_SOURCES})
target_link_libraries(KWinWaylandVirtualBackend kwin)
[platforms/virtual] Use rendernode or vgem device if available for egl Summary: The egl implementation for the virtual platform tries to use a render node if available. If there is no render node it looks for a virtual (kernel driver vgem) device, which unfortunately does not create a render node in mainline kernel (there are patches in ChromiumOS). For this the Udev wrapper is extended to search for renderNode devices and for virtual dri devices. If either render node or vgem dri device is found, it is tried to be opened (without logind escalation) and on success a gbm device is created on it. If any step of this fails the so far default behavior of default device is tried for creating the EGLDisplay. All of this is compile optional, so that the virtual platform does not hard depend on udev and/or gbm. Test Plan: Auto tests which need OpenGL executed and verified that they use the render node or vgem device. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2216
2016-07-19 08:51:09 +00:00
if(HAVE_GBM)
target_link_libraries(KWinWaylandVirtualBackend gbm::gbm)
endif()
[wayland] Add a virtual framebuffer backend A new backend which doesn't present the rendered output. It uses a QPainter scene, renders to a QImage but doesn't present it anywhere. Thus a real virtual backend. By exporting the environment variable KWIN_WAYLAND_VIRTUAL_SCREENSHOTS the backend creates a temporary dir, prints the path to std-out and saves each rendered frame into that directory. Of course with exit it will be deleted again.
2015-10-02 08:44:29 +00:00
install(
TARGETS
KWinWaylandVirtualBackend
DESTINATION
${PLUGIN_INSTALL_DIR}/org.kde.kwin.waylandbackends/
)
Reference in a new issue Copy permalink