- RASPBIAN JESSIE LITE STARTX HOW TO
- RASPBIAN JESSIE LITE STARTX UPDATE
- RASPBIAN JESSIE LITE STARTX DRIVER
- RASPBIAN JESSIE LITE STARTX FULL
- RASPBIAN JESSIE LITE STARTX SOFTWARE
configure -host=armv6-raspberry-linux-gnueabihf -prefix=/usr -disable-rpath -disable-video-opengl I got my test programs to work this way.Ĭonfigure command I used. This forces SDL2 to load the library that goes with X11 instead. If you get the “Could not get EGL display” error, set the SDL_VIDEO_EGL_DRIVER environment variable to libEGL.so.1 or whatever the name is on your system. When launching an SDL application under X11, it tries to load with the Raspberry Pi EGL library which will fail. If the Raspberry Pi is detected as the host, the default library paths get set to the Raspberry Pi ones at compile time.
RASPBIAN JESSIE LITE STARTX DRIVER
The next problem you’ll see now is that the EGL driver selection is a bit stubborn.
RASPBIAN JESSIE LITE STARTX SOFTWARE
Sadly, SDL applications that want to use OpenGL have a bad time now, but software rendering on this slow chip is painful anyway. Then the attribute defaults will work for the Raspberry Pi. There’s the option to build without OpenGL.
This may need some augmenting with environment variables or the hint system. I currently don’t see a way to workaround this one without modifying the application or SDL (unless the developer of the application was smart and built some options into it). The version and profile get set to OpenGL 2.1 and that’s obviously problematic in an OpenGL ES environment. I’ve spotted an issue with the default GL attributes that prevents OpenGL ES contexts from being created when SDL is built with OpenGL. I also think that there should be a separate package if a distribution wants to offer the rpi driver. The distribution repositories usually have the default build configuration which never includes the Raspberry Pi driver. Not in very much detail, but it may give some hints on what is supported and what not. Things might not make sense.įor reference, there’s the README-raspberrypi.md in the SDL source that describes some of these issues.
RASPBIAN JESSIE LITE STARTX FULL
Of course now the large problem is with keyboard input being passed through to the terminal while your full screen app is running.Įdit: The following was written when I didn’t remember the VC4 driver. This works for creating fullscreen SDL2 programs that do not depend on X11. configure -host=arm-raspberry-linux-gnueabihf -disable-video-opengl -disable-video-x11 -disable-pulseaudio -disable-esd -disable-video-mir -disable-video-wayland I was able to get a lib of SDL2-2.0.5 compiled from source working with the RPI video driver and accepting mouse and keyboard input.
RASPBIAN JESSIE LITE STARTX UPDATE
So here an update related to getting input working. It’s a obviously very dangerous situation where running a game can cause arbitrary terminal commands to execute in the background without the users knowledge. I think there is a fix to this problem, but I couldn’t find it using google.
While running an SDL2 program with the RPI video driver, all keyboard input actually is sent your terminal while you program runs. Update below, but first with a big problem.
RASPBIAN JESSIE LITE STARTX HOW TO
If anyone has been able to get an SDL2 lib working on raspberry pi that works as described in the prior paragraph, would you be so kind as to provide some information on how to build such an SDL lib for the pi? I think this information might be useful to others. config options before make’ing SDL2, and I yet to create a lib which works both with the RPI driver (supporting mouse and keyboard input), and the X11 driver (capable of creating a visible floating window). It’s either one or the other with any SDL2 lib I build, but not both. When I boot to the terminal with this lib installed I can create a full screen SDL window relying on the RPI video driver, but I cannot receive any keyboard or mouse events,įinally, I haven’t been able to build single SDL2 lib which can both create a floating window when X11 is running, and create a full screen window when X11 isn’t running. I can however build SDL2 on my pi with RPI video driver support. If I run a test application without X11 running, that is booting straight to the terminal, SDL_GetNumVideoDisplays() returns 0 with the default SDL2 lib and I’m unable to create an SDL window. The default SDL2 in the raspbian jessie repositories only supports and shows X11 as a viable video driver. I am having problems getting SDL2 to work on my raspberry pi without x11 running.