Opened 16 years ago
Closed 12 years ago
#73 closed defect (fixed)
grass64 file has non-general file path
| Reported by: | cnielsen | Owned by: | |
|---|---|---|---|
| Priority: | major | Component: | Package |
| Version: | Keywords: | grass | |
| Cc: | jef@… |
Description
This should be easy to fix. It is the grass64 file in /osgeo4w/apps/grass/bin. Under GISBASE it has "/c/OSGeo4W/apps/grass/grass-6.4.0svn" as default rather than the path that I installed osgeo4w to (not c:\osgeo4w).
Change History (6)
comment:1 by , 16 years ago
follow-up: 3 comment:2 by , 16 years ago
As the terminal seems to be unavailable when starting with the grass.bat icon, personally I would like that file to be left in place. As far as I have found, the only way to keep a functional terminal is to open msys and start grass using this grass64 file (after adding /osgeo4w/apps/grass/bin to PATH in /etc/ini/grass.bat) see <http://trac.osgeo.org/grass/ticket/533>
Also when using msys for other functions (compiling, etc.) it is nice to be able to still start grass from the command line. Is there some way to make both of these function?
comment:3 by , 16 years ago
Replying to cnielsen:
As the terminal seems to be unavailable when starting with the grass.bat icon, personally I would like that file to be left in place.
hm, on Windows grass64.bat and not the grass64 seems to be the intended way to start GRASS. Therefore grass64.bat was customized and copied to /bin for OSGeo4W.
It starts apps/grass/grass-6.4.0svn/etc/Init.bat which in turn starts the text or GUI interface and doesn't leave a command prompt open in the latter case.
So if the current behaviour is not intended Init.bat is the place to change that.
comment:4 by , 16 years ago
Yes as far as I know that's all correct.
I have found a way to modify msys.bat to automatically start grass (using the grass64 file, and therefore init.sh) and have the terminal left available. I think having a terminal is fairly fundamental to grass's functionality, so maybe this approach would be better than having a whole other windows startup system (unless there are more fundamental reasons to having the grass.bat/init.bat).
Basically I just changed line 95 of msys.bat (start %WD%rxvt...) to execute grass64.
comment:6 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
looks like the fix is to remove /apps/grass/bin completely as they are unused and GRASS should be invoked throught grass64.bat in /bin.