-
Notifications
You must be signed in to change notification settings - Fork 466
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
Update bundled SDL2 to 2.0.14 #1078
Conversation
vcpkg CI is failing so might be the cause for the failures related with the Windows version |
Tested in my project using my fork as a dependency and everything worked, no more bottleneck as discussed in the issue. |
Weird that vcpkg fails, you didn't change anything that was related to it... I can see you have changed the folder 2.0.12 into 2.0.14 and renamed the appropriate variable in build.rs. But the diff shows that every file has been renamed without changes: did you just rename the folder, or was the new folder exactly the same as the old one? |
I just renamed the folder, thought it was the appropriate way. Is it not? Its falling only for windows-latest upon building cargo-vcpkg I think |
You are supposed to take the content of this folder https://github.com/libsdl-org/SDL/tree/main/include instead. I think you'll be able to find it in this snapshot of 2.0.14 https://www.libsdl.org/release/SDL2-2.0.14.zip |
@Cobrand I feel a bit dumb 😅 I have now copied everything from the SDL release. Literally all files under |
@joao-conde
According to Microsoft Doc and A post from audacityteam forum: |
I've been using my fork on windows as a project dependency and its works fine, I don't know how the CI windows build fails. |
I test CI under windows-2019(which actually is windows-latest) and windows-2016. |
Closed by #1086 |
@Cobrand opening this for discussion referring to issue #1077 .
I changed what seemed like the relevant code but HAVE NOT TESTED anything because I am unaware of the correct testing procedure. Can you please give me some pointers? Also, feel like this could be added to the README.