2) xeyes, d.mon, d.rast all work ok.
Anything that uses tcltk doesn't, giving:
ERROR: libX11.dll not found in PATH
Note cygwin has recently transitioned to X.org from XFree86.
??
also, any ideas on starting GRASS from the Windows' desktop without
having to type 'startx' and 'grass57'? There isn't enough memory to
leave X running all the time, & the computer is needed for other things.
Cygwin isn't needed for anything else (and if it is, I'm sure the person
who knows UNIX can figure out another way in)
['startx' in .bash_profile and 'exec grass57' in .xsession ?]
Icon attached for motivation.
2) xeyes, d.mon, d.rast all work ok.
Anything that uses tcltk doesn't, giving:
ERROR: libX11.dll not found in PATH
Note cygwin has recently transitioned to X.org from XFree86.
??
also, any ideas on starting GRASS from the Windows' desktop without
having to type 'startx' and 'grass57'? There isn't enough memory to
leave X running all the time, & the computer is needed for other things.
Cygwin isn't needed for anything else (and if it is, I'm sure the person
who knows UNIX can figure out another way in)
['startx' in .bash_profile and 'exec grass57' in .xsession ?]
Icon attached for motivation.
thanks,
Hamish
GRASS 5.7 on Cygwin is very weak. Regarding 1, do you have postgres installed? Regarding 2, I don't know. Cygwin is *very* volitle.
Personally, I use Cygwin/GRASS to do some batch processing on my faster Windows computer, but if I want to use GRASS with a GUI or NVIZ, I use my slower Linux laptop.
Regards,
--
Richard Greenwood
www.greenwoodmap.com
also, any ideas on starting GRASS from the Windows' desktop without
having to type 'startx' and 'grass57'?
startx /usr/X11R6/bin/xterm -e grass57
However, that will only run xterm, and you probably want to run a WM
as well, so create a script, e.g.:
#!/bin/sh
xterm -e grass57 &
exec mwm
then run from another script, e.g.:
#!/bin/sh
/usr/X11R6/bin/startx /path/to/script
Note: the argument to startx has to begin with a slash, otherwise it
won't be interpreted correctly.
There isn't enough memory to
leave X running all the time, & the computer is needed for other things.
Cygwin isn't needed for anything else (and if it is, I'm sure the person
who knows UNIX can figure out another way in)
['startx' in .bash_profile and 'exec grass57' in .xsession ?]
If you always want to run GRASS when starting X, you can add:
xterm -e grass57 &
to ~/.xsession. I suspect you probably don't want to run startx from
~/.bash_profile.
It should be a little better today hopefully. I have made some updates so compiling 5.7 with shared libraries (dlls) on Cygwin should now be possible. Also you can put other shared libraries like GDAL and PROJ in $(GISBASE)/lib and they should be picked up OK (as with 5.3). Please try if you have a chance.
Just to document some other problems with the existing G5.7.0 binaries:
a) NVIZ segfaults in the usual way ('nviz -q' from the command line)
b) d.what.vect gives fails with 'Signal 11' when you click on the
monitor. 'd.what.vect -t' works ok (prints to the console).
And some solutions re. starting cygwin GRASS from an icon on the
windows desktop:
1) running startx automatically:
There is c:\cygwin\cygwin.bat.
I copied that to c:\cygwin\cygwin_goX.bat and edited the last line of
the file to be something like "bash -i --login -c startx". Then I made a
shortcut on the desktop to that batch file. Then right click on the
shortcut to cygwin_goX.bat, set to run minimized & change icon.
2) starting GRASS automatically:
Cygwin ignored .xsession, so I made a ~/.xinitrc file containing the
following: "exec xterm -e grass57".
I've attached to this email a better icon than the last one; a graphics
person might be able to clean it up a little more?
