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

Casing mismatch for WinSDK Include and Lib directories #146

Open
Saancreed opened this issue Oct 24, 2024 · 1 comment
Open

Casing mismatch for WinSDK Include and Lib directories #146

Saancreed opened this issue Oct 24, 2024 · 1 comment

Comments

@Saancreed
Copy link

Hi,

I'm trying to use xwin to cross-compile a C++ project using clang-cl with /winsysroot. I'm preparing the sysroot as follows:

xwin_version=0.6.6-rc.2
curl -sL "https://github.com/Jake-Shadle/xwin/releases/download/${xwin_version}/xwin-${xwin_version}-x86_64-unknown-linux-musl.tar.gz" | bsdtar -xf-
"xwin-${xwin_version}-x86_64-unknown-linux-musl/xwin" \
          --temp --accept-license \
          --arch x86_64 \
          splat \
          --preserve-ms-arch-notation \
          --use-winsysroot-style \
          --output /tmp/winsysroot

Which works almost perfectly, but…

$ ls /tmp/winsysroot/Windows\ Kits/10
include  lib

This doesn't match clang-cl's expectations because it's looking specifically for Include and Lib, which matches Windows SDK installation from my Windows system. A quick ln -s include Include; ln -s lib Lib solves my issue but I'm wondering: why is this different from my Windows VS setup? Shouldn't directories already be named Include and Lib, possibly with lowercase symlinks pointing to them if anything depends on that, so this extra step isn't needed?

@seandunaway
Copy link

thank you, this was incredibly helpful

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

2 participants