-
Notifications
You must be signed in to change notification settings - Fork 204
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
[Build Error][Getting Started] File Path Mismatch in Registry Value (value from get_ucrt_dir
vs actual value)
#405
Comments
miknai
changed the title
[Build Error][Getting Started] Registry value mismatch (value from
[Build Error][Getting Started] File Path Mismatch in Registry Value (value from Sep 4, 2023
get_ucrt_dir
vs actual value)get_ucrt_dir
vs actual value)
Did you install toolchain with Visual Studio installer? We expect it to add these registry keys. |
@KapJI Yes, the toolchain was installed via VS installer before I got the error. |
Wondering if it's the 64 bit vs 32 bit registry? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR
The file path from
get_ucrt_dir
didn't match the file path from the used registry value in my PC (Windows OS).I was stepping through the Getting Started page as a new Buck2 user. Even though followed every step, I encountered the error saying
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'C:\\Program Files\\Windows Kits\\10\\Lib'
while doingbuck2 build //:main
. I took a look atvswhere.py
code below and found out that the file path thatget_ucrt_dir
function finds withKitsRoot10
registry key was different from the actual file path that has the library folder it looks for in my PC.I updated the registry value on my PC, so now the buck2 build works fine. Maybe, a warning should be added in the Getting Started instruction in case other folks get into a similar situation.
The text was updated successfully, but these errors were encountered: