-
Notifications
You must be signed in to change notification settings - Fork 40
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
symlink sdk/lib/<sdkversion> to sdk/lib and sdk/include/<sdkversion> to sdk/include #44
Comments
Oh cool, didn't know those existed! Yes a PR would be very welcome! |
clang-cl version 14 expects "x64" instead "x86_64" for the following three directories:
With
These symlinks could also be added to xwin, but I don't know how to do it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
clang-cl
supports/winsdkdir <dir>
and/vctoolsdir <dir>
in lieu of passing all of the various/imsvc <dir>
and/libpath: <dir>
options to get all of the nested directories for the correct architecture. However, clang's detection of this assumes thatsdk/lib
andsdk/dir
include directories for all of the various Windows SDK versions one could have installed (i.e.sdk/lib/10.0.20348/um/x64
), as this is the layout that Visual Studio uses.Would it be possible to add two additional symlinks in the sdk directory for the Windows SDK version, which just points back to that sdk directory? This would allow compilation command lines to be as simple as
clang-cl --target=x86_64-pc-windows-msvc -fuse-ld=lld-link /winsdkdir /xwin/sdk /vctoolsdir /xwin/crt
, which I think would be a huge convenience win.Confusingly, these symlinks should probably be created even with
--disable-symlinks
so this functionality can still be used on case insensitive file systems.If you're open to adding this functionality, I'm willing to implement and PR it myself.
The text was updated successfully, but these errors were encountered: