-
Notifications
You must be signed in to change notification settings - Fork 6
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 RISC-V build can be fixed #8
Comments
I actually tried this and got it to work. The key elements are:
The last few commits of the PR linked above have the needed changes. Let me know if this is something you'd want and I can create a PR for it. I understand that there is a functional way to get a build for Windows already, but it's not 100% consistent with the build for Linux. |
Thanks - those do look like useful fixes, so if you could raise a PR that would be great |
Sure -- will raise a PR in the next few days. I also noticed that the |
I think a refactor would probably be better in a separate PR? Also, you could probably combine the |
Okay, thanks, I've created a PR for this. |
I was looking at this commit and the associated Actions run.
I saw something similar in my own experiments, and it sounds completely unrelated, but the issue can be fixed by setting
core.autocrlf
tofalse
in the git config. On Windows the build.ps1 file is used to clone needed repos so you could likely just add-c core.autocrlf=false
to the command line there:pico-sdk-tools/build.ps1
Line 180 in 178ced3
(Or set it globally beforehand, it's a throwaway CI runner.)
The text was updated successfully, but these errors were encountered: