fix(build): static-link MinGW package-smoke to fix CI hang

The installed-package smoke exe dynamically linked the MinGW runtime; the Windows runner resolves a mismatched libstdc++/libgcc/winpthread on PATH, hanging the exe at startup/teardown (same root cause as the earlier test-exe STATUS_ENTRYPOINT_NOT_FOUND). Embedding the GCC runtime makes it self-contained and PATH-independent, without changing what the smoke verifies. Verified locally: exe carries no external GCC runtime DLL and exits 0.

Author: tkhquang

tests/package_smoke/CMakeLists.txt

@@ -11,5 +11,14 @@ find_package(DetourModKit REQUIRED)
 add_executable(dmk_package_smoke main.cpp)
 target_link_libraries(dmk_package_smoke PRIVATE DetourModKit::DetourModKit)
 
+# Statically link the GCC runtime on MinGW. This is a CI-runner workaround, not a consumer recommendation: a
+# Windows runner can resolve a mismatched libstdc++ / libgcc / libwinpthread on PATH than the toolchain that built
+# the exe, which makes the smoke binary hang at startup/teardown. Embedding the runtime makes it self-contained so
+# the installed-package check is PATH-independent, without changing what is verified here (find_package wiring and
+# the exported C++23 requirement).
+if(MINGW)
+  target_link_options(dmk_package_smoke PRIVATE -static -static-libgcc -static-libstdc++)
+endif()
+
 enable_testing()
 add_test(NAME dmk_package_smoke COMMAND dmk_package_smoke)