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>

On Windows 10 1909 ScrollConsoleScreenBufferA() returns an error if
the destination is not within the clip rectangle but still modifies the
console buffer as expected! So mark this behavior as very_broken().

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54871

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

This allows changing the location of activation context stack if it
should be put somewhere else (e.g. inside the fiber structure).

This refactoring makes it easier to change the algorithm of obtaining
the current activation context stack.

This refactoring makes it easier to change the algorithm of obtaining
the current activation context stack.

Note that RtlAddRefActivationContext(NULL) is a no-op, and
check_actctx(NULL) returns NULL without doing anything.

According to Geoff Chappell's information.

Depending on the DNS server, querying test.winehq.org may point to CDN
servers, resulting in more records than expected.
Also some of the CDN servers may have IPv6 addresses.
Dump the DNS records if $WINETEST_DEBUG > 1.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54847