Hey! raylib forum is closing!
After a year with not much movement in the forum I decided to close it.
The cost of maintaining the hosting is a bit high for the usage of the platform, updating the forum and managing it is also a bit cumbersome and the truth is that I'm already trying to maintain multiple other networks pretty more active than this forum.
I'll recommend you to move to the other raylib networks:
- For a forum style, use Reddit: https://www.reddit.com/r/raylib/
- For direct messaging and questions, use Discord: https://discord.gg/VkzNHUE
- To report issues, use GitHub: https://github.com/raysan5/raylib
- Also, remember you can contact me personally on Twitter: https://twitter.com/raysan5
or directly by mail to ray[at]raylib.com
If you feel generous, you can also contribute to the project on my Patreon: https://www.patreon.com/raylib
Thanks to you all for joining the project and help to improve it with your questions. Keep it up! :)
PD. Closing will be effective by October 31th.
Now having Raspberry pi raylib installation problems
In preparing to use raylib for a raspberry pi class, I tried to install another version of raylib
on a second raspberry pi 3. This first of all was of course updated to the latest raspbian
and the packages updated using the usual pi commands
sudo apt-get update and sudo apt-get dist-upgrade.
I then copied the raylib folder onto this new machine and followed the raysan5/raylib "Compile for Raspberry Pi" instructions page.
I did the sudo apt-get install libopenal1 libopenal -dev with no problem
I tried to compile raylib using make PLATFORM=PLATFORM_RPI and this time it failed with the following:
make: C:/SysGCC/Raspberry/bin/arm-linux-gnueabihf-gcc: Command not found
Makefile:357: recipe for target 'core.o' failed
I do not know what I did correctly the first install to get raylib up without problems.
Compiling my own examples on the second machine also fails.
Perhaps my copy of raylib is not correct in some way, best to start again, perhaps you could recommend exactly
where to get the pi version from (perhaps it is no different from the windows version) or any other possibility you see.