Unable to build a crate using the latest 'windows' crate and no import in my IDE
⚓ Rust 📅 2025-10-07 👤 surdeus 👁️ 5Hello everyone,
I am having trouble building a simple program using some Windows API calls using the "windows" crate.
I am facing 2 mains issues :
Issue 1 :
I added the windows crate & other crate to help me manipulate strings. During the building phase, the rust compiler throws an large number of ' use of unresolved module or unlinked crate `windows_*'. Having skimmed though the changelog on the release section of the crate, I did notice that a lot reworking has been done between the 0.5X version to the 0.62 version, though I am not expiremented enough to fully understand that changes I need to apply to even make a single windows pop.
The Cargo.toml is very short and only has the following :
[dependencies]
widestring = "1.2.0"
windows ={ version = "0.62.1", features = ["Win32_Foundation", "Win32_NetworkManagement", "Win32_System_SystemServices", "Win32_System_Threading", "Win32_System_WindowsProgramming", "Win32_UI_WindowsAndMessagin
g"] }
windows-strings = { version = "0.4.2", features = ["std"] }
Issue 2 :
I am using Helix as IDE and therefore am relying on the rust-analyzer to generate inlay-hints to code. I can't import the symbols resolutions from the windows crate within my IDE.
Any advice is much appreciated for I am lost in the limbs...
2 posts - 2 participants
🏷️ Rust_feed