I've been experimenting with CopperSpice on the Raspberry Pi 5 and wanted to share my experiences and see if others have tackled this as well. I'm targeting a headless setup, leveraging OpenGL ES for rendering.
So far, I've managed to cross-compile CopperSpice 2.0.0 using the standard Raspberry Pi build tools. However, I'm running into some performance bottlenecks, particularly with larger graphical applications. I'm curious if anyone has optimized their builds for the Raspberry Pi 5 specifically?
Has anyone had success using different OpenGL ES drivers (e.g., Mesa, Broadcom)? Any tips on profiling and identifying performance hotspots in CopperSpice applications running on ARM? Also, if anyone's tried using the Yocto Project to create a custom CopperSpice-based image for the Pi, I'd be interested in hearing about your experiences!
I'm also considering using a custom compilation of the sources to optimize the builds even more and get the best possible performance.
CopperSpice on ARM - Raspberry Pi 5.
Re: CopperSpice on ARM - Raspberry Pi 5.
Thank you for your interest in the CopperSpice project.
We build CopperSpice for Raspberry Pi by cross compiling in a Debian 12 Docker image. For an introduction to our recommended build environment for Raspberry Pi using a GCC arm cross-compiler and QEMU, please review the following CS Overview documentation.
https://www.copperspice.com/docs/cs_overview/build-pi.html
Let us know if you have further questions.
We build CopperSpice for Raspberry Pi by cross compiling in a Debian 12 Docker image. For an introduction to our recommended build environment for Raspberry Pi using a GCC arm cross-compiler and QEMU, please review the following CS Overview documentation.
https://www.copperspice.com/docs/cs_overview/build-pi.html
Let us know if you have further questions.
Ansel Sermersheim
CopperSpice Cofounder
CopperSpice Cofounder