I noticed that most of the *.bat files have forward slashes. For example: C:\OSGeo4W\apps\grass\bin\grass64.bat: set WINGISBASE=/c/OSGeo4W/apps/grass/grass-6.4.0RC4 C:\OSGeo4W\apps\grass\grass-6.4.0svn\bin\d.correlate.bat: @"%GRASS_SH%" -c '"%GISBASE%/scripts/d.correlate" %*' C:\OSGeo4W\apps\grass\grass-6.4.0svn\etc\Init.bat: if "%GRASS_PROJSHARE%"=="" set GRASS_PROJSHARE=/c/OSGeo4W/share/proj C:\OSGeo4W\bin\grass64.bat set WINGISBASE=%OSGEO4W_ROOT%/apps/grass/grass-6.4.0svn
Why is there 2 grass64.bat? Bob Moskovitz Research Analyst I Seismic Hazard Evaluation Project California Geological Survey http://gmw.consrv.ca.gov/shmp CONFIDENTIALITY NOTICE: This communication is intended only for the use of the individual or entity to which it is addressed. This message contains information from the State of California, California Geological Survey, which may be privileged, confidential and exempt from disclosure under applicable law, including the Electronic Communications Privacy Act. If the reader of this communication is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. > -----Original Message----- > From: Glynn Clements [mailto:[email protected]] > Sent: Monday, June 22, 2009 7:22 PM > To: Moskovitz, Bob > Cc: Grass-User (E-mail) > Subject: RE: [GRASS-user] Problems with GRASS python code in osgeo4w > > > > Moskovitz, Bob wrote: > > > There is no etc/python/grass/script/core.py. Just > > etc\python\grass.py. > > That changed in the last month or so, but I don't think that it has > any bearing on this. > > > Here is a part of a pdb debug session: > > > > > > c:\osgeo4w\apps\grass\grass-~1.0sv\etc\python\grass.py(208)parser() > > I don't like the look of the "grass-~1.0sv" bit. > > > -> if sys.platform == "win32": > > (Pdb) > > > > c:\osgeo4w\apps\grass\grass-~1.0sv\etc\python\grass.py(209)parser() > > -> try: > > (Pdb) > > > > c:\osgeo4w\apps\grass\grass-~1.0sv\etc\python\grass.py(210)parser() > > -> os.execvp("g.parser.exe", [name] + argv) > > (Pdb) p [name] + argv > > > ['c:\\osgeo4w\\apps\\grass\\grass-6.4.0svn\\scripts\\m.dipslop > e.py', 'c:\\osgeo > > 4w\\apps\\grass\\grass-6.4.0svn\\scripts\\m.dipslope.py'] > > (Pdb) > > That much looks okay. > > > I debugged a bit deeper with pdb and found this: > > (Pdb) > > > > c:\osgeo4w\apps\grass\grass-~1.0sv\etc\python\grass.py(210)parser() > > -> os.execvp("g.parser.exe", [name] + argv) > > (Pdb) s > > ==================== snip > =============================================== > > > c:\warmerda\release\apps\python25\lib\os.py(389)_execvpe() > > -> func(fullname, *argrest) > > (Pdb) p fullname > > 'c:\\osgeo4w\\bin\\g.parser.exe' > > (Pdb) PATH > > ['c:\\osgeo4w\\bin', > 'C:\\OSGeo4W/apps/grass/grass-6.4.0svn\\bin', 'C:\\OSGeo4W/ > > apps/grass/grass-6.4.0svn\\lib', 'C:\\OSGeo4W\\bin', > 'C:\\Perl\\bin\\', 'C:\\WIN > > DOWS\\system32', 'C:\\WINDOWS', > 'C:\\WINDOWS\\System32\\Wbem', 'C:\\Perl\\bin\\' > > ,'C:\\WINDOWS\\system32', 'C:\\WINDOWS', > 'C:\\WINDOWS\\System32\\Wbem'] > > > > There is no c:\osgeo4w\bin\g.parser.exe but there is a > C:\OSGeo4W\apps\grass\grass-6.4.0svn\bin\g.parser.exe. > > This is a red herring. os.execvp() iterates through PATH, attempting > each directory in turn until it succeeds. > > However, the fact that the GRASS bin and lib directories have forward > slashes might be a problem. Try correcting PATH from the command line > first. > > -- > Glynn Clements <[email protected]> > _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
