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] opengl enabled, but sdl configured with opengl disabled #689
Comments
This test checks that your SDL headers define |
Unsure as to how my particular SDL package was built, as I just installed whatever the default one was with dnf. Attaching the contents of my SLD_config.h |
update: |
That header appears to be owned by
Native SDL2 is supported, and finds its headers on its own. If you need help with that, please provide the logs from the failed build. |
Sorry for the late response. Here's my situation. I have both sld2 and dls12-compat installed, but it still says the header is missing. If it's officially supported, I guess I'd prefer to try native sdl2 just because I want to help test, but I don't see any documentation on how to build with it (or is scons supposed to automatically detect it? If it is, it's not working...). |
Since SDL1 and SDL2 can be concurrently installed, SCons does not automatically pick one over the other. It presently defaults to SDL1, but you can pass |
Hmm... That's what I tried, but it's still telling me that it can't find SDL.h. sdl2=1 just goes after the scons command, right? |
Yes. |
A similar report from a Gentoo user is now listed in the Gentoo bug tracker at https://bugs.gentoo.org/show_bug.cgi?id=900212 . It does not provide the requisite log to confirm the problem, but that user also is using a package that uses SDL2 to emulate SDL1. I am inclined to consider this a bug in the emulation package, since it purports to work like SDL1, but does not behave like SDL1. |
OS: Fedora 37 (GNOME) x86_64
I installed the packages in INSTALL.txt (SLD_image-devel was not found, but was listed as optional so I ignored) and ran scons, but it stopped with the following full output:
Attaching sconf.log that the error mentions.
sconf.log
The text was updated successfully, but these errors were encountered: