So, this is mostly my fault, but there are several things at play which have contributed to the general neglect of ROS on OS X.
First off, I got a lot of things working in Diamondback and Electric while I was in graduate school. During the Fuerte release my involvement decreased due to my thesis work. So, that has contributed to the neglect of more recent ROS releases in OS X.
Additionally, Homebrew and Apple have been shaking things up. In the last year we have seen the default compiler change (gcc to clang), the packaging of Xcode change (moving the command line tools to an external installation), X11 for OS X ownership change, a new version of Homebrew (0.9), and bunch of other smaller things in the Homebrew/Apple world that have basically introduced all kinds of small problems. These are mostly easy to fix, but there are a lot of them and they are understandably annoying when end users run into them.
Finally, ROS is currently transitioning to a new build system called catkin. This is going to make supporting non-debian systems much easier, but it is still not stable, but should be with in the next three weeks (groovy api freeze). Along with catkin is a rework of the release system, which should again make it simpler to support OS X and other platforms moving forward. I have held off working on making OS X a "first" class ROS OS because I don't want to have to rework things when these new systems land, instead I have been trying to keep up-to-date with them and make sure that the end product is something that lends itself to OS X support.
Currently, the only way to install ROS on OS X is via the "source" install where you download, build, and install the code manually. The quality of these source install instructions have declined for Fuerte and even the once stable Electric instructions. I would appreciate any help maintaining these instructions from the community, as I don't have time to constantly install ROS from scratch on OS X to find new problems. For all the faults in the Fuerte source install instructions, I have successfully built and run rviz and rqt_gui for example, so it is possible, just not polished.
The bigger goal than having good source install instructions is having easier installation methods. With the new systems (catkin and bloom) all ROS stacks/packages (even third party ones) will generate Homebrew formulae in parallel with debian src packages. This will allow you to do things like brew install ros/fuerte/desktop-full
and get everything downloaded, built, and installed via Homebrew. This will remove some of the burden from the OS X community and encourage package/stack maintainers to maintain their code for OS X.
Taking that a step further, once the formulae are auto generated, we can put the formulae into the build farm, where they can be built and tested. Failing builds and ... (more)