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.

Sign up for GitHub

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

Jump to bottom

WindowsSdkDir vs WDKContentRoot #8

Open
clouds56 opened this issue Apr 26, 2019 · 3 comments
Open

WindowsSdkDir vs WDKContentRoot #8

clouds56 opened this issue Apr 26, 2019 · 3 comments
Assignees
@SergiusTheBest

Comments

@clouds56
Copy link

I'm using VS2019 and WDK 10, WindowsSdkDir is automatically set while WDKContentRoot not.
Could we add some kine of fallback to WindowsSdkDir?
@clouds56 clouds56 mentioned this issue Apr 27, 2019
Closed
@SergiusTheBest
Copy link
Owner

I'm not sure I understand the problem. Could you describe it a little bit more? WDK is still in C:/Program Files*/Windows Kits/10 nevertheless what version of Visual Studio you use.

@SergiusTheBest SergiusTheBest self-assigned this May 9, 2019
@clouds56
Copy link
Author

clouds56 commented May 9, 2019

I'm using WDK installed in custom location, namely C:/Kits/10, and after running C:\Program Files(x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" (I think most person would run it before using msvc), the environment variable WindowsSdkDir would properly set to C:/Kits/10, while WDKContentRoot not

@SergiusTheBest
Copy link
Owner

@clouds56 Could you make a separate PR for it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SergiusTheBest SergiusTheBest

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add WSDK::<LIBRARY>
2 participants
@clouds56 @SergiusTheBest