#580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run ---------------------------+------------------------------------------------ Reporter: hamish | Owner: [email protected] Type: defect | Status: new Priority: blocker | Milestone: 6.4.0 Component: wxGUI | Version: 6.4.0 RCs Resolution: | Keywords: wingrass Platform: MSWindows XP | Cpu: Unspecified ---------------------------+------------------------------------------------ Comment (by hamish):
> Replying to [comment:15 cmbarton]: > > Why can't windows use g.gui gui=[guiplatform] -nu? Replying to [comment:16 cnielsen]: > This command does work in the msys command prompt (native > installer r40049), with this followed by g.gui &, you can > switch back and forth with no problem. * this is hardly as user friendly as a GUI which asks: "use Wx", "use Tcl", or "use text" & restart. these wrapper scripts are not designed for power users who are comfortable with the command line. * the default osgeo4w build does not give the user a msys prompt, although I guess you could try the Cmd> prompt if you knew the exact magic incantation. * v.type from a GUI is impossible and needs a wrapper. > > There is a problem running python scripts in GRASS for Windows. it's just a bug, and not a fundamental problem. mere details can and will be fixed. > > A regular Python installation will properly put Python in > > the registry so that it can be called to execute scripts. we ''should'' have the equivalent already set up in the msinstaller startup batch files and scripts to associate .py with a suitable python.exe. check this bug's previous comments & grep the msinstaller scripts for more. but that isn't working for some reason. Hamish -- Ticket URL: <https://trac.osgeo.org/grass/ticket/580#comment:19> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
