-
Notifications
You must be signed in to change notification settings - Fork 7
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
Raspberry Pi 2 build #17
Comments
It should continue to build even when the build script outputs this error, do you get any error messages? |
Libtools was Not installed for some reason but I did not think that was an issue. I installed libtools and removed all the SDL2 componients and tried again. it goes on a few lines after that and says SDL2 is installed at usr/lib/ or something like that. I'll have to run it again when I get home to see the exact location it said. But it does not go any further. Is there a verbose mode on the build.sh? |
Afraid not. Only mupen64plus makefiles can be verbose if you use V=1 ./build.sh. I have tried to build the script to output a meaningful error message if the scrip fails. What line does the script fail on? |
It fails I think on line 333 of build.sh, it says "SDL2 2.0.3 located at ..." And then just quits. I am still not home to actually print exactly what it said but that is what I recall, and it's pretty close. |
Ok. I am dumb and did not give it enough memory because I thought the boosted memory could handle it. I set GPU memory to 32MB. However, Now I am runing into SDL2 not being compiled with GLES. ../../src/api/vidext_sdl2_compat.h:34:2: error: #error SDL is not build with OpenGL ES2 support. Try USE_GLES=0 I am asuming that the RPI has the GLES 2 headers somewhere that is unusual and SDL2 cannot find them when it compiles. Going back and looking at the SDL2 checks for GLES, the output is: checking for OpenGL ES v1 headers... no Also I would like to note that when I did compile the build.sh for the second time around SLD2 gave me a warining: libtool: install: warning: remember to run `libtool --finish /usr/local/lib' Which as the script kept running it failed at: ../../src/api/frontend.c:30:17: fatal error: SDL.h: No such file or directory So I did `libtool --finish /usr/local/lib' to remedy this and it continued untill it failed where it told me SDL2 was not compiled with GLES. I am not sure where the GLES2 headers are on the raspberry pi. |
GLES2 headers are normally installed by default with Raspbian. Can't remote in to check for you but think they are in /opt/vc/. If they are no where on your system then they can be downloaded from official raspberrypi repo |
pi@raspberrypi /opt/vc/include $ ls They seem to be there. Do you have any idea why SDL2 did not find them? |
Maybe SDL2 got confused due to script failing so could you try running: CLEAN=1 CLEAN_SDL2=1 ./build.sh It will try and configure and rebuild everything again so sorry for the 2h wait. |
I will try that. Cout it be that SDL2 does not know that it is a Raspberry pi 2? I think it just tries to build it as armv7. |
@gizmo98 knows more about compiling for Pi2. I tink SDL2 should still compile but you will need some tweaks to the RaspianList file for Pi2 I think. |
I've created a new Build list for the Pi2. You should only need to use the following command to get Pi2 optimizations: ./build.sh RaspbianList_Pi2 |
I think I got SDL2 to build with GLES2. ./configure --disable-video-opengl --disable-video-x11 CPPFLAGS=-I/opt/vc/include SDL2 Configure Summary: It is compiling now and I will report back soon. |
Alright! I got everything to complie properly. Took me a while and it probably could be done better but here is what I did. I am pretty sure that the ./configure in SDL2 does not have a specific instructions for the Raspberry Pi 2 and therfore does not know where the VC libraries are. It just assumes it is a generic Armv7 device. SDL2 variables: sudo ./configure --disable-video-opengl --disable-video-x11 --host=armv7l-raspberry-linux-gnueabihf --enable-video SDL2 Configure Summary: I think that others might run into the same problem when compling from just the build.sh. I was looking at Retropie and how they compile SDL2 and the invoke something similar in their script. I am not sure if I am using the armv7 compiler to its full potential as it was jus trial and error to get it to complie the video driver and GLES2 support. Also, Even with the RPI2 list NEON did not properly build in GLES2N64, had to add another CFLAG to the ifdef statement to get it to properly compile. CFLAGS += -mfpu=neon |
Is there a test I can do in the build script e.g. uname or /pro/cpuinfo to distinguish between pi and pi2? |
You can use uname and test armv6l (rpi) and armv7l (rpi2). |
cheers |
Added test for armv7l and armv6l so should build without needin to pass in Pi2 list |
This problem is still not fixed. Not sure why this one was closed. You have to add following to the SDL_CFG in build.sh to let SDL2 find the EGL/Gles2 headers:
|
Same problem :( |
I am having the EXACT same problem on Raspberry Pi 3 model B. I am new to both Linux and the Pi. I have tried everything in this forum so far and nothing has worked. Any suggestions?!? Or more info that I can give you? |
Fresh build on a Raspberry pi 2.
SDL2 is missing the Raspberry PI Driver. You will not be able to run mupen64plus in the console.
I keep running into this and it won't continue the build. What can do? I have tried to run autoconf on SDL2 and build again but that did not help.
The text was updated successfully, but these errors were encountered: