Tom Atkinson

> FWIW, you could probably just skip the vcpkg step on windows, since using whatever cmake provides to download and compile sources is functionally equivalent to how vcpkg is currently...

Removed vcpkg in favour of CPM 

WASM was a little soul destroying but I got there :tada: [Changes specific for WASM support](https://github.com/wolfpld/tracy/pull/707/commits/b38cfead85f4da7a3b68a5a7ce981579c9deccbf) ``` emcmake cmake -Bbuild -S. -DCMAKE_BUILD_TYPE=Debug cmake --build build --target profiler ``` Gives this...

Added back `.vscode/launch.json` support. As the build is now using cmake it no longer needs to be platform specific. Because of this i renamed unix to native to make it...

Bonus: Launch Emscripten Application Builds and compiles the WASM into `build/emscripten/bin` and runs using `launch,json` 

@YaLTeR Im not sure we need to touch the Meson as it looks like this only depends on `public`, `common` and `client` which i have left in place? The current...

Build matrix latest run is mostly green https://github.com/tomadamatkinson/tracy/actions/runs/7381214753 This is missing running the test at the moment. I want to spend some time to make sure i get it right....

Hey @wolfpld, Thanks for the feedback. I went down a whole rabbit hole yesterday! I appreciate you taking the time to look at it further In terms of VSCode and...

@wolfpld I've sorted out pulling system dependencies instead of fetching. If users prefer fetching they can set `TRACY_FORCE_FETCH_DEPENDENCIES` I've been researching the CMake Tools extension. Although there is a separate...

Variants might be a valid solution I got this by adding a `cmake-variants.json` (can also be yaml)  We can then selectively expose targets and set options using  This...