The tar balls of cross-compilers tend to come nowadays with python support, e.g. arm-none-eabi-gdb-py, but this not yet the case for python3, there's no arm-none-eabi-gdb-py3 binary.
This means that your much appreciated code won't work out of the box for developers who don't compile their cross-compilers themselves.
The following commit is still python-2 compatible:
git checkout 76fe009847a3551ee56e75d4d0fa340977943c24
However, maybe it's nice to tag that release (or maybe a later release which is still not python3) and indicate that towards the users of this repository in the README.md? Or alternatively, create a python2 branch and cherry-pick a few of the bugs that have been fixed over time.
Thanks for your work, much appreciated!
The tar balls of cross-compilers tend to come nowadays with python support, e.g.
arm-none-eabi-gdb-py, but this not yet the case for python3, there's noarm-none-eabi-gdb-py3binary.This means that your much appreciated code won't work out of the box for developers who don't compile their cross-compilers themselves.
The following commit is still python-2 compatible:
However, maybe it's nice to tag that release (or maybe a later release which is still not python3) and indicate that towards the users of this repository in the
README.md? Or alternatively, create apython2branch and cherry-pick a few of the bugs that have been fixed over time.Thanks for your work, much appreciated!