[GRASS-dev] Re: [GRASS GIS] #623: compiling error grass6-devel - winvista 32

2009-05-31 Thread GRASS GIS
#623: compiling error grass6-devel - winvista 32 --+- Reporter: hellik | Owner: grass-dev@lists.osgeo.org Type: defect | Status: closed Priority: normal

Re: [GRASS-dev] GRASS 6 swig compile error

2009-05-31 Thread Glynn Clements
Markus Neteler wrote: /home/neteler/grass64/swig/python/raster_wrap.c:3777: undefined reference to `unlock_driver' Fixed in r37598 (in 6.5). I still see cd lib/raster [nete...@host550 raster]$ svn up At revision 37598. [nete...@host550 raster]$ grep unlock_dr * rem_io.c:extern

[GRASS-dev] Re: [GRASS GIS] #620: Platform.make odd variables settings

2009-05-31 Thread GRASS GIS
#620: Platform.make odd variables settings ---+ Reporter: frankie | Owner: grass-dev@lists.osgeo.org Type: defect| Status: new Priority: normal|

Re: [GRASS-dev] any idea about these python libraries?

2009-05-31 Thread Glynn Clements
William Kyngesburye wrote: Nothing in GRASS should link directly to them on OSX. Only wxpython modules should link to the wx libraries, vdigit just loads wxpython. I found that wx nviz and vdigit *did* link the wx libraries - a reversion in the switch to setup.py that I missed.

Re: [GRASS-dev] any idea about these python libraries?

2009-05-31 Thread Michael Barton
I think the issue is that wx libraries are in 2 places on the Mac: 1) in /usr/lib/ installed with the system and 2) in /usr/local/lib/wx- python... for the libraries that are installed with a new installation of wxPython. The latter is what is pointed to in the config statement and it seems

[GRASS-dev] Re: [GRASS GIS] #623: compiling error grass6-devel - winvista 32

2009-05-31 Thread GRASS GIS
#623: compiling error grass6-devel - winvista 32 --+- Reporter: hellik | Owner: grass-dev@lists.osgeo.org Type: defect | Status: closed Priority: normal

[GRASS-dev] grass7 on WinGrass Multi.make deps

2009-05-31 Thread Hamish
Hi, while reviewing streamlining the WinGrass build instructions I notice a work-around is given for the grass 7 Make/Multi.make file which looks like it might be a bug. It is step 4 for building GRASS 7: https://trac.osgeo.org/grass/wiki/CompileOnWindows#Grass-7.0.svntrunk -$(BIN)/%$(EXE):

[GRASS-dev] bound_box in python

2009-05-31 Thread Danho Fursy Rodelec Neuba
Can you tell me howto use bound_box in python. I am new in grass developping and i use python. I need to use Vect_get_map_box and bound_box* type is requiered. ___ Yahoo! Mail réinvente

Re: [GRASS-dev] bound_box in python

2009-05-31 Thread Markus Neteler
On Sun, May 31, 2009 at 12:45 PM, Danho Fursy Rodelec Neuba danh...@yahoo.fr wrote: Can you tell me howto use bound_box in python. I am new in grass developping and i use python. I need to use Vect_get_map_box and bound_box* type is requiered. In theory it should be import os, sys from

Re: [GRASS-dev] any idea about these python libraries?

2009-05-31 Thread William Kyngesburye
You can check which wx libraries are linked with (before my change in SVN): otool -L /path/to/grass/etc/wxpython/nviz/_grass6_wxnviz.so And compare that with the sys.path in Python - the wxpython path for the installed new wxpython should be before any system path. On May 31, 2009, at

Re: [GRASS-dev] any idea about these python libraries?

2009-05-31 Thread William Kyngesburye
On May 31, 2009, at 3:51 AM, Glynn Clements wrote: I found that wx nviz and vdigit *did* link the wx libraries - a reversion in the switch to setup.py that I missed. Fixed now in SVN. Code which calls wx functions directly *should* be explicitly linking against the wx libraries. Even if you

[GRASS-dev] Re: [GRASS GIS] #623: compiling error grass6-devel - winvista 32

2009-05-31 Thread GRASS GIS
#623: compiling error grass6-devel - winvista 32 --+- Reporter: hellik | Owner: grass-dev@lists.osgeo.org Type: defect | Status: closed Priority: normal

[GRASS-dev] Re: [GRASS GIS] #623: compiling error grass6-devel - winvista 32

2009-05-31 Thread GRASS GIS
#623: compiling error grass6-devel - winvista 32 --+- Reporter: hellik | Owner: grass-dev@lists.osgeo.org Type: defect | Status: closed Priority: normal

Re: [GRASS-dev] Re: PROJ csv files sync GDAL - GRASS?

2009-05-31 Thread Markus Neteler
On Tue, Apr 28, 2009 at 12:57 PM, Paul Kelly paul-gr...@stjohnspoint.co.uk wrote: On Sat, 25 Apr 2009, Markus Neteler wrote: On Sun, Apr 19, 2009 at 9:21 PM, Paul Kelly wrote: I think we can remove the files and the associated stuff you mentioned if these conditions are true:  * The .csv

Re: [GRASS-dev] grass7 on WinGrass Multi.make deps

2009-05-31 Thread Glynn Clements
Hamish wrote: while reviewing streamlining the WinGrass build instructions I notice a work-around is given for the grass 7 Make/Multi.make file which looks like it might be a bug. It is step 4 for building GRASS 7: https://trac.osgeo.org/grass/wiki/CompileOnWindows#Grass-7.0.svntrunk

Re: [GRASS-dev] bound_box in python

2009-05-31 Thread Glynn Clements
Markus Neteler wrote: but I get Traceback (most recent call last): File examples/vectoraccess.py, line 45, in module print 'Map box:', grassvect.Vect_get_map_box(map, box) TypeError: in method 'Vect_get_map_box', argument 2 of type 'BOUND_BOX *' Using instead BOUND_BOX, it also

Re: [GRASS-dev] any idea about these python libraries?

2009-05-31 Thread Glynn Clements
William Kyngesburye wrote: I found that wx nviz and vdigit *did* link the wx libraries - a reversion in the switch to setup.py that I missed. Fixed now in SVN. Code which calls wx functions directly *should* be explicitly linking against the wx libraries. Even if you can rely upon

Re: [GRASS-dev] grass7 on WinGrass Multi.make deps

2009-05-31 Thread Hamish
Hamish wrote: while reviewing streamlining the WinGrass build instructions I notice a work-around is given for the grass 7 Make/Multi.make file which looks like it might be a bug. It is step 4 for building GRASS 7: https://trac.osgeo.org/grass/wiki/CompileOnWindows#Grass-7.0.svntrunk