I echo the need to focus on the GUI tools, that would benefit from the graphics acceleration when running natively on macOS (my pain-point). The other ros processes can always be run in containers during development.
If we set these goals:
- Fix ros2 source build/install on macOS, upping support to Big Sur, M1 CPU
- Fix Gazebo build for Big Sur/M1 (actually I don’t know if it builds or not, haven’t tried)
- Binary distribution of GUI tools such as rqt, rviz, gazebo with Homebrew
then what is the appropriate tool to track this effort? A meta issue? in which repo? A github’s project? I would appreciate some direction how to organize this.
I currently have a build locally on Big Sur + M1/arm64, with rviz building and running. Lot’s of hacks/workarounds. I would like to start consolidating these workarounds so we can track the fixes in ros2 and upstream projects.
