[GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question
Yang, Bo (yangb2)
yangb2 at mail.uc.edu
Mon May 9 18:40:44 PDT 2016
Hi Helmut and Moritz,
Thanks for the reply and advise, here is my updates:
> > no error reported in former steps either, and I can see the file "
> > grass71svn.bat " is located in the right place.
> what is the "right place"? what is the path to the "right place"?
According to the tutorial , after compile with the default setting, the grass71svn.bat should be located in " c:\osgeo4w\bin\grass71svn.bat.". I see it is there, but when I run it via cmd (or double click), it always give the error:
'""' is not recognized as an internal or external command,
operable program or batch file.
Press any key to continue . . .
> > SET OSGEO4W_ROOT=@osgeo4w@
> could it be that OSGEO4W_ROOT isn't defined?
> was winGRASS also installed or eventually only compiled?
Win GRASS was not installed yet, because in the tutorial the step of "Creating a WinGRASS Installer" was located after the step of "Compiling and Installing GRASS GIS". And the tutorial mentioned: " Do not move on to step two until you have successfully tested your new version of GRASS. "
So I didn't install WinGRASS since my compile part didn't go through yet.
>compare OSGEO4W_ROOT above. OSGEO4W_ROOT has to be defined, otherwise the other bat-files, which define all needed variables, and grass71.py can't be found.
I edit the grass71svn.bat file compare with your file.
I change line " SET OSGEO4W_ROOT=@osgeo4w@ " of the bat file to " SET OSGEO4W_ROOT=C:\osgeo4w64 " since my path is C:\OSGeo4W64\bin.
I run the grass71svn.bat again and poped up the below error:
I Googled the missing dll solutions and copy them from C:\OSGeo4W64\bin to C:\osgeo4w64 and run again. Then it shoed on the screen:
Cleaning up temporary files...
Starting GRASS GIS...
ERROR: wxGUI requires wxPython. No module named wxversion
ERROR: Error in GUI startup. See messages above (if any) and if necessary, please report this error to the GRASS developers.
On systems with package manager, make sure you have the right GUI package, probably named grass-gui, installed.
To run GRASS GIS in text mode use the -text flag.
Press any key to continue . . .
I think this time is most close to start compiled GRASS so far.
>Yes, I agree: don't worry about Lidar at this stage. You should be able
>to just ignore these errors and run GRASS anyhow. Have you tried running
>it after this compile?
I found that if the compile result have errors, there are no file of grass71svn.bat in the path of C:\OSGeo4W64\bin. So I don't know how to ignore the error and run GRASS anyway because on the tutorial the grass71svn.bat is needed for start GRASS.
From: Moritz Lennert [mailto:mlennert at club.worldonline.be]
Sent: Monday, May 9, 2016 3:40 AM
To: Helmut Kudrnovsky <hellik at web.de>; grass-dev at lists.osgeo.org
Subject: Re: [GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question
On 09/05/16 08:26, Helmut Kudrnovsky wrote:
> For MS windows have a look here:
>> I assume win10 is too new so I tried win 7 and win8.1 using different
>> computers. I
> AFAIK the Windows version doesn't matter.
>> Errors in:
> please check if the development dependencies for the lidar tools are
> present in your build development.
> install them or disable to build them (maybe the latter is better in
> Windows 64bit as there may be some issues with the las tools in
> OSGeo4W 64bit AFAIR).
Yes, I agree: don't worry about Lidar at this stage. You should be able to just ignore these errors and run GRASS anyhow. Have you tried running it after this compile ?
More information about the grass-dev