Build system upgrade

[tmp64]

1. Replace pre-built binaries with vcpkg packages
2. Replace complicated Python scripts with CMake's built-in install functionality
3. Generate final release ZIPs on GitHub Actions
4. Generate AMXX offsets automatically on every build
5. Write new build instructions: https://github.com/tmp64/BugfixedHL-Rebased/wiki/Compiling-guide

Closes #232

[tmp64]

@rtxa Can you check if you can build this branch using the new instruction?

[rtxa]

Well, I have moved to VSCode since then and it didn't require too much configuration on my side, only to have installed VS 2022 with desktop C++ workload and VSCode extensions for C++ and CMake and I was good to go (I did all the HUD thing in there).

Probably the new build system is better but I'm not getting it to compile when using VSCode. Do I need to have vcpkg installed before hand? I think requisites/prerequisites should mention that to be clear. Seems like I need to have installed Ninja because I'm getting this error even with vcpkg configured.

Can all this be downloaded before hand when doing CMake configuration? I think that the fewer things the developer has to install or configure, the better.

[tmp64]

Thanks for testing. Regarding your errors: vcpkg is working properly ("All requested installations completed successfully" in the log). But CMake can't find Ninja.

I updated the guide and added sections explaining Ninja and VS Code. I use clangd and CodeLLDB extensions instead of C/C++ extension because, in my experience, they work better (on Windows with MINGW and on Linux), so I used them in the guide. Let me know if they work correctly on Windows.

[rtxa]

Sorry but I'm still not getting it to compile, something related to the target, I already renamed CMakeUserPresets.json and I'm using user-debug

[tmp64]

I updated CMakeUserPresets.example.json and added user-debug-vscode to make it simpler. And I fixed the error.

[rtxa]

In CMakeUserPresets.json, you missed naming user-debug in configurePreset the same as in name, otherwise it would not show any user preset.

Anyway, some other problems arise:

When using user-debug-vscode

When using user-debug-vs2022

Perhaps we can arrange a time where I would share my screen to you on Discord? So we can get to the root of the problem quickly.

[tmp64]

I finally figured it out. Turns out you don't even need Ninja, VSCode can use "Visual Studio 17 2022" generator. And you don't need clangd and CodeLLDB in that case. I updated the docs, CMakeUserPresets.example.json, .vscode/launch.example.json and .vscode/config.example.json. It should work now.

[rtxa]

Good, now it works!

Question: With the previous workflow, I could select if I want to build for Debug, Release, etc. How can I do this now? Debug variant as default worries me because it triggers asserts when doing normal playing.

[tmp64]

I updated the presets.

1. Split Windows and Linux presets into different includes. Now there is only one user preset instead of separate user-windows and user-linux presets.
2. Added separate user build presets: user-debug and user-release. I added a section about this to the docs.