Bug report #7697
GRASS commands, OS X not working
|Affected QGIS version:||2.4.0||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||not reproducable|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||16610|
On OS X, there are a few different approaches for installing QGIS and dependencies. On my machine, I use a package manager called homebrew, similar to dpkg or similar in the linux world.
When grass is installed from source on OS X, there are some differences from what is done on linux. Homebrew grass creates a shell script and names it grass64 rather than grass.sh. This script is found in /usr/local/bin, not in the bin path where all of the grass binaries are kept.
On testing a possible solution today to get the grass provider operating for myself, I noticed that sextante is expecting to find grass.sh in the same folder path that I set in the grass provider options for the "GRASS Folder". This is the binary directory where my v.*, r.* and other grass binaries reside.
To get grass working, I created a symlink from my grass64 shell script to grass.sh in the "GRASS Folder". My test of v.voronoi worked as expected. I have not tested further.
Instead of requiring the mac user to hack a fix for this, I would recommend that an additional setting be added to the grass provider options to point to the grass shell command. In my case, I would set this to point at the grass64 command. An alternative would be to set the name for the grass shell command, in my case the setting would be 'grass64'. As grass64 is in my PATH under /usr/local/bin, this should also be sufficient to overcome the problem.
#1 Updated by John Tull about 8 years ago
See my note here also: