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
- MSVC-specific code is used in some places and compiled only if _MSC_VER is set; however, Clang under Windows also defines this, which reports errors on this non-standard code if the -pedantic-errors compiler flag is set
Fix MSVC Warning C4244: 'argument': conversion from 'uint64_t' to
'uint32_t', possible loss of data
We only store 32 bit thread ids in ThreadNameData.
Trying to follow existing style instead of static_cast.
Fix#723: Memory: active allocations are incorrectly displayed in call stack tree
The range we were looking for was wrong (should be Active instead of
Inactive), but I also reworked to make the comparison clearer.
Test
Using the repro app from the bug:
1. Click "Free + Allocate" once
1. Call stack tree shows 2 entries under "Active allocations", 1 active
allocation, 0 inactive allocations in the call stack tree.
1. Click "Free + Allocate" several times
1. Call stack tree shows 1 KB of active allocations and many KB of
inactive.
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.
