unom/punktfunk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 17 Wiki Activity

ci(windows-drivers): static-CRT .cargo/config (fixes StaticCrtNotEnabled)

Browse Source 
wdk-build errored StaticCrtNotEnabled + the generated wdk-sys layout asserts
overflowed (E0080) — UMDF needs the static CRT. Add the canonical
windows-drivers-rs .cargo/config.toml: explicit target = x86_64-pc-windows-msvc
(separates host proc-macros, which stay dynamic-CRT, from the driver) +
target-feature=+crt-static scoped to that target. DLL now under the triple subdir.

The WDK bindgen itself now runs (it generated out/types.rs) — this is the last
build-config layer before the /INTEGRITYCHECK verdict.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Enrico Bühler
2026-06-24 08:52:40 +00:00
parent 6e3239c4b6
commit ce7367bff2
2 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packaging/windows/drivers/.cargo/config.toml
+12
View File
@@ -0,0 +1,12 @@
# windows-drivers-rs requires UMDF drivers to link the STATIC CRT (wdk-build errors `StaticCrtNotEnabled`
# otherwise, and the generated wdk-sys bindings' layout asserts only hold with it).
#
# Setting an EXPLICIT build target is the trick that makes `target-feature=+crt-static` apply ONLY to the
# driver cdylib and NOT to host build-scripts/proc-macros (which must stay dynamic-CRT): with an explicit
# --target, cargo compiles host artifacts for the implicit host and the `[target.<triple>]` rustflags
# apply only to the target. The Windows host (and thus its drivers) is x64-only by design.
[build]
target = "x86_64-pc-windows-msvc"
[target.x86_64-pc-windows-msvc]
rustflags = ["-C", "target-feature=+crt-static"]