The library migrated from 'make build-python' + 'pip install bindings/python'
to a scikit-build-core + cmake build where the entire repo root is pip-
installable via 'pip install .'. Update first_time_install.sh accordingly:
- Remove the 'make build-python' step (target no longer exists)
- Install directly from the repo root instead of bindings/python
- Replace build deps: remove cython3/scons/python3-dev, add python-dev-is-python3
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Configure submodule to track upstream master branch (branch = master in
.gitmodules) so future updates are a single 'git submodule update --remote'
rather than manual SHA management.
Update first_time_install.sh to use --remote flag so fresh installs always
pull the current upstream master, not the commit recorded at clone time.
Current upstream HEAD (8907235) brings:
- PR #1886: Raspberry Pi 5 support — new RP1 PIO and RIO backends. The
library auto-detects Pi 5 hardware at runtime; no config change required
for basic operation. adafruit-hat-pwm is confirmed supported on Pi 5.
- PR #1833: setup.py migrated from distutils → setuptools, fixing Python
3.12+ build failure (Pi runs Python 3.13). Previous version could not
build the bindings at all on current Pi OS.
Expose new rp1_rio option in display_manager.py and config.template.json:
0 (default) = PIO mode — uses Pi 5 RP1 coprocessor, minimal CPU usage
1 = RIO mode — Registered IO, faster throughput, higher CPU; note that
gpio_slowdown has inverted effect in this mode
No API changes to RGBMatrix, RGBMatrixOptions, or FrameCanvas. Pi 4 and
earlier hardware is unaffected — rp1_rio is silently ignored on non-Pi-5.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
