Switch to CMake and fix compilation with VS2022
Author: mrexodiaCreated Aug 4, 2024Updated Sep 14, 2026
Labelspriorityinfrastructure
This has been on my personal roadmap for a while, but wanted to add an issue to track it.
- Add a CMakeLists.txt in parallel to x64dbg.sln
- Support VS2022:
- Fix all warnings
- Fix Visual Studio analyzer results
- Add TitanEngine/GleeBug as submodules
- Add an option to automatically download a supported Qt5 LTS version (VS2019)
- Integrate clang-tidy
- Clean up the project root
- Support “offline” builds (ready-to-compile source package)
- Create an external plugin for Scylla (latest fork)
- Upgrade dbghelp.dll and msdia140.dll to the latest version
- Restore delayed imports
- Restore signing functionality for latest MSVCRT
- Remove TitanEngine/DeviceNameResolver and other internal libraries from the pluginsdk
- Update compilation instructions in the wiki
- Update the QtPlugin template and PluginTemplate
- Delete the old
.vcxprojandx64dbg.profiles - Fix the relative submodule path when forked (
url = ../../x64dbg/deps) - Make sure the
exeproject is the default startup project in the generated solution - Update CONTRIBUTING.md to match the new workflow
- Remove licenses from
docsfolder and pull them dynamically during the build to avoid multiple licenses being detected for the repository
Source: x64dbg/x64dbg