Open Boscop opened 6 years ago
Trying to rule out the possibility that there's something funky going on with your build environment, so bear with me here:
I have Windows sdk 8.1. Plain old cmd.exe. Shouldn't this crate be able to find the location of the sdkl through the registry? :)
It does, by querying HKLM\SOFTWARE\Microsoft\Microsoft SDKs\Windows\[SDK. version]
, which is redirected to Wow6432Node on 64-bit Windows. (winres uses a different key, but AFAICT that one doesn't distinguish between versions). Apparently in the past, a similar subkey was created under HKCU
, but IIRC modern installs don't do this anymore - could it be that you don't have the HKLM subkey but do have the HKCU one?
Hm, apparently I have the HKLM key (but not the older HKCU key):
Ah, I see now. This is an earlier a different version of the Windows 8.1 SDK, as indicated by the A
suffix (the one that ships with Visual Studio 2017 doesn't have this). find-winsdk doesn't check for these right now, only v10.0
and v8.1
. Fixing this should be pretty simple, although we won't be able to test for it on CI because, at least when using the VS2017 image, older versions of the Windows SDK aren't pre-installed on AppVeyor.
windres 0.2.1, which addresses this issue, is published on Crates.io. Could you run a cargo update
and see if it works?
I tried it in cmd.exe, it didn't work:
Maybe it can't find the winsdk or rc.exe from the registry?
Btw, the
winres
crate worked...