Knowning that frame->code will be set when the exception handler
is called.  Suppress this coverity issue.

Instead of multiplying it by 2.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54808Co-authored-by: Nikolay Sivov <nsivov@codeweavers.com>

If lpSectionBase is null then the tests will still crash, but at least
we'll know why.

Use the xdg-output-unstable-v1 protocol to get the size of the Wayland
outputs in the compositor logical space, and use this information, along
with the logical position and size in physical pixels (i.e., the current
mode) to infer the Windows virtual screen coordinates of the monitors.

Note that there are multiple possible mappings from Wayland logical
coordinates to Windows virtual screen coordinates. We choose one
algorithm that works well for the majority of output arrangements, and
we can refine in the future as needed.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Use the xdg-output-unstable-v1 protocol to get the positions of the
Wayland outputs in the compositor logical space, and use this
information to arrange the monitors in the Windows virtual screen space.
For now we assume that the logical positions match the physical pixel
positions (i.e., the outputs are not scaled), a deficiency which will be
addressed in an upcoming commit.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Use the xdg-output-unstable-v1 protocol to get a unique, cross-process
consistent name for the outputs.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

Wayland protocol descriptions are distributed as source XML files that
need to be transformed to C source and header files with a version of
the wayland-scanner tool compatible with the used libwayland library.

This commit enhances the makedep build tool to support building such
Wayland protocol XML files.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>

After the driver process initialization is done, use all the received
wl_output information to non-forcefully initialize the display devices.
We will reintroduce dynamic display device reinitialization (i.e., as a
response to non-initial wl_output events) when we start reading and
dispatching Wayland events.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>