Windows build fails

[St3veSmith]

Following command line instructions with CMake, most packages install as expected.

Command line:

cmake -B profiler/build -S profiler -DCMAKE_BUILD_TYPE=Release
cmake --build profiler/build --config Release --parallel

Second step fails with:

Checking File Globs
  1>Checking Build System
  Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Apps > Advanced app settings > App execution aliases.

Assuming need to install Python here (but I'd rather not if possible), but unclear which version.

Attempting to build the visual studio, most files build but consistently get error:

tracy\profiler\src\HttpRequest.cpp(8,10): error C1083: Cannot open include file: 'GitRef.hpp': No such file or directory
tracy\profiler\src\main.cpp(71,10): error C1083: Cannot open include file: 'GitRef.hpp': No such file or directory

[wolfpld]

but unclear which version.

Is this a problem? How many versions are out there?

[St3veSmith]

I had assumed it would not be a problem, but installing python latest directly, as well as ensuring the visual studio install has python included (which it does) still fails from the commandline with CMake. Same "missing python" error building from VSCode.

Attempting to build directly in visual studio from the provided .sln also fails with missing GitRef.hpp, so it does look like a missing dependency (Git is installed, with all available options).

So, currently on Windows, following all instructions from the PDF, build consistently fails:

• Visual Studio 2022 .sln: Missing GitRef.h
• CMake commandline: missing python (despite python latest installed for Visual Studio 2022, VSCode, and latest python download)
• VSCode: Same errors as CMake commandline (not surprisingly).

[St3veSmith]

So it turns out downloading and installing Python directly or through VSCode doesn't actually work; on windows you have to download and install Python from the Microsoft Store specifically for it to work. Might be worth adding a note in the docs to that effect to save headaches (but running that line from the makefile uncovered this pretty quickly).