Unity’s MonoDevelop Won’t Start on OSX
I ran into this problem the first time that I installed Unity, and I
just encountered it again after upgrading to Unity 4.3. When I launch
the IDE the MonoDevelop logo shows briefly in the dock before
disappearing but MonoDevelop doesn’t start.
Here’s a little detail on my setup:

Now when you click on a script, Unity will launch MonoDevelop from the new location, and it seems to be happy with the write permissions. If I get some time over the weekend I may try figuring out what exactly the problem is so I can submit it.
Here’s a little detail on my setup:
- Mac OSX 10.9
- I generally run as a non-admin user.
- Unity 4.3, MonoDevelop-Unity 4.0.1
- Move the MonoDevelop app from the default location in your applications directory to a directory where your user has write permissions. For example, mine goes in ~/Applications.
- In Unity, select Preferences > External Tools > External Script Editor.
- Choose Browse… and select the path where you put MonoDevelop in step 1. Make sure that this is set as the external editor in Preferences.

Now when you click on a script, Unity will launch MonoDevelop from the new location, and it seems to be happy with the write permissions. If I get some time over the weekend I may try figuring out what exactly the problem is so I can submit it.
Comments
Post a Comment