-
-
Notifications
You must be signed in to change notification settings - Fork 226
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 build warning: SDL_GetRevisionNumber #542
Comments
Hi @wushu037, could you try with the latest version which is |
Hi @veeableful , thank you very much, I tried it and now it compiles successfully. |
Hi @wushu037, it seems like you have already asked in the right place! If you need a fix now, I think you may be able to just simply use older SDL2 versions such as 2.0.12 or maybe even 2.0.14. On second look, it seems like the error is just a warning so maybe you were able to compile it? Did it produce the |
Hi @veeableful , thank you for your interest! 1. I modified to the latest version and the warning is gone 2. oh, indeed. I updated the issue in gobot, thank you. And when I compiled it on a Mac with the cross-platform compilation script provided in the readme for go-sdl2, not only did I get a warning from go-sdl2, but I also got a fatal error from robotgo. This caused me to describe the warning as an error in the description, so sorry about that To be honest, I don't know how to fix this at the moment, because I'm not very familiar with that cross-platform compilation script provided by go-sdl2 |
Hi @wushu037, I think you could try using Docker or Podman to run the cross-compilation under Linux which seems to be a supported way of cross-compiling for robotgo. If you want to cross-compile on macOS, you might need to build zlib using the mingw-w64 tools so robotgo can use it but it might be more troublesome than just using Linux container to do it. |
I got an error when I tried to compile the windows platform
(Both compiling with cross-platform and compiling directly on windows gave me an error)
macos to windows
windows
The text was updated successfully, but these errors were encountered: