"Fossies" - the Fresh Open Source Software Archive

Member "qt-everywhere-src-6.3.1/qtwayland/README" (8 Jun 2022, 2945 Bytes) of package /linux/misc/qt-everywhere-src-6.3.1.tar.xz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 This is the QtWayland module.
    2 
    3 The QtWayland module consists of two parts:
    4 
    5 Wayland platform plugin:
    6     Enables Qt applications to be run as Wayland clients.
    7 
    8 QtWaylandCompositor API:
    9     Enables the creation of Wayland compositors using Qt and QtQuick.
   10 
   11 To build the QtWayland module you need the external dependencies:
   12 xkbcommon - http://xkbcommon.org/
   13 wayland - http://wayland.freedesktop.org/
   14 
   15 QtWaylandCompositor supports loading client buffer integrations that don't use
   16 the wayland-egl interfaces. These client buffer integrations are picked up by
   17 QtWaylandCompositor as plugins. To specify what plugin to load use the environment
   18 variable QT_WAYLAND_CLIENT_BUFFER_INTEGRATION in the environment where the
   19 compositor is started. The compositor will broadcast to the clients which
   20 hardware integration to load when using the generic platformplugin "wayland". If
   21 no client buffer integration is specified, then the wayland-egl plugin will be
   22 loaded. Please note that no Weston clients will work if the non standard
   23 wayland-egl client buffer integration is used.
   24 
   25 Available client buffer integrations are:
   26 wayland-egl (this is the default)
   27 linux-dmabuf-unstable-v1
   28 brcm
   29 
   30 Testing a Qt-based compositor on X11:
   31 
   32 Most QWidget-based applications will use shared memory buffers, which work on
   33 all hardware. OpenGL and Qt Quick applications need a way to send graphics
   34 memory buffers from client to server. There are many options, and not all
   35 options work on all hardware.
   36 
   37 Using wayland-egl requires support from the driver. Intel integrated graphics
   38 are supported through the standard Mesa drivers. For NVidia, driver version
   39 364.12 or newer is required, and Qt must be configured with "-opengl es2".
   40 Run the compositor as follows:
   41 
   42 QT_XCB_GL_INTEGRATION=xcb_egl QT_WAYLAND_CLIENT_BUFFER_INTEGRATION=wayland-egl ./minimal-qml
   43 
   44 Please note that some NVidia drivers may require early EGL initialization. Qt
   45 clients normally use the buffer integration communicated by the compositor.
   46 To set the client-side buffer integration manually, run clients with
   47 "-platform wayland-egl".
   48 
   49 Shell Integration:
   50 
   51 Some platforms, especially non-desktop ones, use a custom Wayland shell
   52 extension. These are tailored to the specific embedded form factor better than
   53 the generic wl_shell or xdg_shell extensions that target desktop systems.
   54 Custom shell protocols are added through shell integration plugins.
   55 
   56 Which shell integration to use is determined by the QT_WAYLAND_SHELL_INTEGRATION
   57 environment variable. If no shell is specified, the default is to try shells in
   58 the following order: xdg-shell, xdg-shell-v6, wl-shell and then ivi-shell.
   59 
   60 Example Usage:
   61 
   62 Starting the hellowindow example application (one of the examples for qtbase)
   63 with ivi-shell integration:
   64 
   65     QT_WAYLAND_SHELL_INTEGRATION=ivi-shell ./hellowindow -platform wayland
   66 
   67 Available Shell Integrations:
   68 
   69     * ivi-shell
   70     * wl-shell (deprecated)
   71     * xdg-shell
   72     * fullscreen-shell-v1
   73