Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows SDK 26100 splits headers into more msi files #128

Closed
greaka opened this issue Jun 23, 2024 · 2 comments
Closed

Windows SDK 26100 splits headers into more msi files #128

greaka opened this issue Jun 23, 2024 · 2 comments
Assignees

Comments

@greaka
Copy link
Contributor

greaka commented Jun 23, 2024

I was chasing down an issue where winapifamily.h couldn't be found during a build. On old installations it still worked though.
After 3 weeks I finally figured out why it fails.

Starting with 10.0.26100, the windows sdk headers are split into the previously existing packages plus 4 new onecoreuap variants. The shared directory for example was completely moved out of the windows store apps headers package and into the windows store apps headers onecoreuap package, which also includes the missing winapifamily.h.

Here is an example entry for a onecoreuap package:

{
    "fileName": "Installers\\Windows SDK for Windows Store Apps Headers OnecoreUap-x86_en-us.msi",
    "sha256": "9234C4395D3C17673AEC0A7D32556AA85ADEDA0E3FDE8EF92C13601F844E0E6B",
    "size": 462848,
    "url": "https://download.visualstudio.microsoft.com/download/pr/e7508e1c-f746-4f1d-a5f0-74020753cca5/3dded07e9e6da4546077e58eaf5c8c44/windows%20sdk%20for%20windows%20store%20apps%20headers%20onecoreuap-x86_en-us.msi",
     "cache": false,
     "signer": {
         "$ref": "4"
     }
}

xwin fails to search and install these msi packages. I believe the correct location to add this would be when pruned.push() inside get_sdk is called.

Like in #126, reverting back to older sdk versions fixes my issue.

@memory-thrasher
Copy link

seconded. SDL needs this too, via winsdkver.h

@Jake-Shadle
Copy link
Owner

Resolved in #129

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants