Remove obsolete MFC prerequisites and replace outdated assembler images
with version checks. Clarify release configurations, Spectre libraries,
and signing instructions.
Verified the guide end-to-end on a clean Windows 11 + VS2022 Community
17.14 machine (Release|x64 and Release|Win32 both build with 0 errors).
Fixes for the issues found along the way:
- Recommend a current NASM release instead of 2.08 (2010); NASM 2.16.03
verified against all assembly sources. Fix the Path example for the
64-bit installer location.
- Simplify YASM setup: the build only invokes yasm.exe from the Path.
Drop the zip/vsyasm download and the YASMPATH system variable, which
nothing in the build references.
- Add a "Common build errors" section to Known Issues mapping the three
errors every default VS2022 install hits (MSB8040 Spectre libs, C1083
atlbase.h, MSB8066 exit 9009) to the components that fix them.
- Explain why the Release|Win32 pass is needed (Setup/Portable/COMReg
are only built by that configuration).
Addresses #1488.
Co-authored-by: 0xDarkMatter <0xDarkMatter@users.noreply.github.com>
Replace outdated Visual Studio 2010/2019 and legacy Windows SDK 7.1, WDK 7.1, and Windows 8.1 SDK guidance with the current Visual Studio 2022/v143 toolchain, Windows 10/11 SDK, and WDK requirements.
Document NASM, YASM, WiX Toolset v3.x, signtool.exe, and optional legacy BIOS bootloader tools separately. Update the build flow for x64, ARM64, Win32 setup/helper projects, and explicit Driver project builds.
Align the zh-cn and ru translated guides with the updated English content while preserving their existing translation style. Fix test certificate paths to use src/Signing/TestCertificate.
* Documentation: Remove XHTML spec and fix errors
None of the docs follow the XHTML specification, which means
that programs that expect this (such as Gnome Web) as it is advertised
as such, will completely fail to parse it as it is incorrect syntax. So
it is removed.
* Remove .chm files
Mounir IDRASSI
JertzukkaandGitHub
Mounir IDRASSI