Temp: Remove CI
linux dependencies
auto download dependencies
install libs with choco
name artifacts
use LINK_LIBRARIES
add concurrency
install dependencies
install dependencies
install dependencies
passwordless sudo
windows fix
more windows fixes
more windows fixes
no statistics
On wl_compositor >= 6 we bind v6 and use preferred_buffer_scale.
Otherwise we bind 4 and do as before.
No other changes are needed for the version bump as Tracy doesn't use
wl_surface_attach() with nonzero coordinates.
On Wayland the scale now changes to the correct value as the Tracy
window is moved across monitors.
If the scale is overridden from environment, it does not change, just
like before.
Wayland kindly informs us which outputs the surface is on, to be used
for scale computation (at least on wl_compositor < 6). On mixed DPI
setups this fixes Tracy potentially using a higher scale than the output
it's displayed on.
However, as is, this commit results in Tracy always using scale 1,
because at the point of backend creation (which is when the scale is
queried) the surface is not yet displayed on any outputs, so a scale of
1 is assumed.
`zxdg_toplevel_decoration_v1` isn't a global, so the code handling it as
one wasn't doing anything. Instead,
`zxdg_decoration_manager_v1_get_toplevel_decoration` returns it.
This fixes the behavior for compositors that support server-side
decoration, but do not default to it until explicitly requested by the
client.
wasm-ld: error: /home/wolf/.emscripten_cache/sysroot/lib/wasm32-emscripten/lto/libc-mt.a(ntohs.o): attempt to add bitcode file after LTO.
wasm-ld: error: /home/wolf/.emscripten_cache/sysroot/lib/wasm32-emscripten/lto/libc-mt.a(htonl.o): attempt to add bitcode file after LTO.
