I have also been using grass7 on windows using the msys shell
(installed in a path without spaces). The GUI works fine though I
haven't tried this kind of python script.
nb. I am not using a self-installed Python, but the copy that comes
with the windows native installer. If the windows PATH or PY
The wxpython dir was moved to gui/wxpython (r41557) by martinl. If
you're getting the same error as I was then then this should fix it.
The error was:
Starting GRASS ...
WARNING: Attention!
WARNING: Locking is not supported on Windows!
c:\programs\gis\osgeo4w\bin\python.exe: can't open file
'c:/pr
Michael Barton schrieb:
> In a related question, maybe more for Colin, does GRASS 7 work in Windows?
> If so, what is the setup to allow it to run the scripts in Python?
I'm compiling from time to time Grass7 in the osgeo4w-stack on a WinVista32-box
for myself.
AFAICT grass7 on WinVista is w
#1026: Problems starting grass7 from tcsh
--+-
Reporter: huhabla | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Jordan Neumeyer wrote:
> > > Just kind of my thought process about how I would try to go about
> > > parallelizing a module.
> >
> > The main issue with parallelising raster input is that the library
> > keeps a copy of the current row's data, so that consecutive reads of
> > the same row (as hap
OK. This helps. We were trying it in the "MSys' (broken and deprecated) rxvt
program".
Like I said, I'm not familiar enough with Windows to realize that this would
not work. I'm trying to help get python GRASS scripts to work under Windows. So
testing it from MSys is not the way to go. Should w
Michael Barton wrote:
> I just updated from the svn and built GRASS 7. Initially, it gave an
> error for the wxpython gui. But when I switched to the gui dirctory and
> ran make, it all compiled fine. So it seems that something in the make
> file is not working correctly for the gui.
What error,
Michael Barton wrote:
> We've tried the things below and are not getting anywhere. I don't know
> if we simply don't understand something (I'm not a Windows person, but
> the 2 students copied are) or there is something more we need to do.
>
> So far, we've installed Python from python.org. We'v
Needs an edit to lib/init/functions.sh line 263.
{{{
@@ -260,7 +260,7 @@
# ok
if [ "$?" = 0 ] ; then
# Set the wxpython base directory
- WXPYTHONGRASSBASE="$ETC/wxpython"
+ WXPYTHONGRASSBASE="$ETC/gui/wxpython"
else
# Python was n
> Colin (Nielsen) Wren wrote:
>Same here on Vista. The wxpython dir is missing from the build dir.
>
>osgeo4w\bin\python.exe: can't open file
>'c:/programs/gis/osgeo4w/apps/grass/grass-7.0.svn/etc/wxpython/gis_set.py':
>[Errno 2] No such file or directory
>
>Something to do with r41557?
>
>On 31 Ma
Opps, forgot to send this to mailing list as well...
On Tue, Mar 30, 2010 at 8:32 PM, Jordan Neumeyer <
jordan.neume...@mines.sdsmt.edu> wrote:
> Hi Glynn,
>
> On Tue, Mar 30, 2010 at 8:29 AM, Glynn Clements
> wrote:
>
>>
>> Jordan Neumeyer wrote:
>>
>> > Just kind of my thought process about ho
+1 for OpenCL
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
#1026: Problems starting grass7 from tcsh
-+--
Reporter: huhabla | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
On Thu, Apr 01, 2010 at 12:50:12AM -0700, Hamish wrote:
> As I understand it, CUDA is 100% dependent on the closed-source binary
> driver from nVidia and works on their video cards alone. Which is fine
> for today for people with nVidia hardware using their binary video
> card driver. If nVidia dec
Markus wrote:
> http://grass.osgeo.org/wiki/GPU
added-
As I understand it, CUDA is 100% dependent on the closed-source binary driver
from nVidia and works on their video cards alone. Which is fine for today for
people with nVidia hardware using their binary video card driver. If nVidia
decides
15 matches
Mail list logo
