/home/vasek/dev/grass/trunk/lib/external/shapelib/dbfopen.c
/home/vasek/dev/grass/trunk/lib/external/shapelib/shpopen.c
I can't see any KR style declarations in these files. It's possible
that the SHPAPI_CALL macro is confusing Doxygen.
It is easy to confuse Doxygen. Thanks for the fix.
On 20 March 2013 03:01, Yann Chemin yann.che...@gmail.com wrote:
yes r.patch is a good alternative, but it means writing to disk etc.
Was more thinking of a display memory thingy.
Unfortunately, in wxGUI maps are rendered to files (by d.* modules)
and then read to wxGUI. (That's probably why it
Hi, I am trying to compile grass 7.0 (revision 55463). I am getting a lot
of errors, with the first folder with error the 'lib/raster3d'
Going there and running make gives me the following:
gcc -g -O2 -fPIC
-I/home/paulo/Software/spatial/grass7_trunk/dist.x86_64-unknown-linux-gnu/include
I am on it ...
2013/3/20 Paulo van Breugel p.vanbreu...@gmail.com:
Hi, I am trying to compile grass 7.0 (revision 55463). I am getting a lot of
errors, with the first folder with error the 'lib/raster3d'
Going there and running make gives me the following:
gcc -g -O2 -fPIC
Hi,
sorry, that was my fault. I have committed the correct 3D raster
library header files. Revision 55464 should work now.
Best regards
Soeren
2013/3/20 Paulo van Breugel p.vanbreu...@gmail.com:
Hi, I am trying to compile grass 7.0 (revision 55463). I am getting a lot of
errors, with the first
On 19/03/13 19:04, Michael Barton wrote:
I think that this is a good idea for GRASS 7. We shouldn't really do it
with GRASS 6.
+1
Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On 19/03/13 20:57, Markus Neteler wrote:
If you accept me to manage the release and related stuff, I am happy
to prepare things as needed with your help.
Great ! And yes, I'm willing to help on this.
No need to rush, though. I think the secret of success of the schedule
is preparation and
On Wed, Mar 20, 2013 at 10:17 AM, Ivan Barka ivan.ba...@gmail.com wrote:
Hi devs,
so now I can configure G7 (revision 55464) on AIX 7.1 by command:
export PATH=$PATH:$HOME/apps/bin
CFLAGS=-lstdc++ ./configure --prefix=$HOME/apps
--with-proj-includes=$HOME/apps/include
On 3/20/13, Sören Gebbert soerengebb...@googlemail.com wrote:
Patch that removes the buggy LRE compression has been applied to trunk
#55462. Tests for 3D raster modules and the library passed
successfully. The patch should assure backward compatibility.
I hope i did not break anything. :)
The
On Wed, Mar 20, 2013 at 11:08 AM, Markus Metz
markus.metz.gisw...@gmail.com wrote:
On Wed, Mar 20, 2013 at 10:17 AM, Ivan Barka ivan.ba...@gmail.com wrote:
Hi devs,
so now I can configure G7 (revision 55464) on AIX 7.1 by command:
export PATH=$PATH:$HOME/apps/bin
CFLAGS=-lstdc++
Hi,
recently I have updated Mediawiki version for our GRASS-wiki to the
latest stable version 1.20.3 (copied from git) [1]. Enjoy new
features:-), if you consider any extension which could be useful for
our wiki, please contact me.
Best regards, Martin
[1]
On Wed, Mar 20, 2013 at 11:50 AM, Markus Metz
markus.metz.gisw...@gmail.com wrote:
...
GNU make 3.81 and GNU install are available in the official IBM AIX
toolbox as well as third-party AIX software repositories.
See also:
http://grasswiki.osgeo.org/wiki/Compile_and_Install#AIX
(...Markus M
Thanks!
On Wed, Mar 20, 2013 at 9:23 AM, Sören Gebbert soerengebb...@googlemail.com
wrote:
Hi,
sorry, that was my fault. I have committed the correct 3D raster
library header files. Revision 55464 should work now.
Best regards
Soeren
2013/3/20 Paulo van Breugel p.vanbreu...@gmail.com:
Yann,
About all I can recommend is the vrt format tutorial,
http://www.gdal.org/gdal_vrttut.html, gdal, data model
http://www.gdal.org/gdal_datamodel.html, and driver tutorial,
http://www.gdal.org/gdal_drivertut.html , etc in the gdal online
documentation. You might look at the existing
Funny Doug, you nearly read my mind here... - gdal/GRASS interface code
Thanks,
Yann
On 20 March 2013 17:29, Newcomb, Doug doug_newc...@fws.gov wrote:
Yann,
About all I can recommend is the vrt format tutorial,
http://www.gdal.org/gdal_vrttut.html, gdal, data model
By at least, do you mean looking at 2.6, 2.7 or 3.0 as well?
Doug
On Tue, Mar 19, 2013 at 2:04 PM, Michael Barton michael.bar...@asu.eduwrote:
I think that this is a good idea for GRASS 7. We shouldn't really do it
with GRASS 6.
I like going to at least Python 2.5 also.
Michael
Good question, maybe a roadmap ending (so far with Python 3 for Grass
8 (funny to mention this version number !)
On 20 March 2013 17:32, Newcomb, Doug doug_newc...@fws.gov wrote:
By at least, do you mean looking at 2.6, 2.7 or 3.0 as well?
Doug
On Tue, Mar 19, 2013 at 2:04 PM, Michael Barton
On Wed, Mar 20, 2013 at 12:02 PM, Newcomb, Doug doug_newc...@fws.gov wrote:
By at least, do you mean looking at 2.6, 2.7 or 3.0 as well?
+1 for python 2.6 that it is the default version in debian stable [0]...
Moreover, the Python 2.6 [1] added compatibility functions in a
future_builtins
Hi,
I just wanted to ask how the quiet-flag is defined. I mean, what
will be still reported to the screen (console)? How is it with
self-written e.g. add-ons
in python. If quiet is set are all grass output messages
automatically suppressed?
What about the status report of counting percentages
Martin Landa wrote:
2013/3/20 Nikos Alexandris n...@nikosalexandris.net:
I feel that trac makes it difficult (for me) to write and structure the
text for a ticket. I am forced to manually enter [[BR]] to break lines!
putting extra empty line do the job for me. For preformatted text use
#1903: r.watershed fails with Subprocess failed with exit code 6
-+--
Reporter: marcosc | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal
Minimum wxPython version is changed in r55466 (I hope I haven't missed
any other places).
On Wed, Mar 20, 2013 at 1:31 PM, Pietro peter.z...@gmail.com wrote:
On Wed, Mar 20, 2013 at 12:02 PM, Newcomb, Doug doug_newc...@fws.gov wrote:
By at least, do you mean looking at 2.6, 2.7 or 3.0 as well?
My understanding is that Python 3 is not backward compatible with Python 2.
Michael Barton
School of Human Evolution Social Change
Center for Social Dynamics Complexity
Arizona State University
...Sent from my iPad
On Mar 20, 2013, at 8:26 AM, Anna Kratochvílová kratocha...@gmail.com wrote:
Hi Michael,
On Wed, Mar 20, 2013 at 3:35 PM, Michael Barton michael.bar...@asu.edu wrote:
My understanding is that Python 3 is not backward compatible with Python 2.
it is true, but we are not talking to require python3 instead of
python2, we are talking to require python2.6 instead of
On Wednesday 20 of March 2013 16:11:19 Vaclav Petras wrote:
BTW, I'm not able to find edit a ticket, although I think that it is
possible. (There are some projects which don't want to change original
ticket descriptions.)
Believe me, I was looking for it too, right after I submitted, of course
On Wed, Mar 20, 2013 at 3:59 PM, Nikos Alexandris
n...@nikosalexandris.net wrote:
Martin Landa wrote:
2013/3/20 Nikos Alexandris n...@nikosalexandris.net:
I feel that trac makes it difficult (for me) to write and structure the
text for a ticket. I am forced to manually enter [[BR]] to break
Some information :
Python 2.5 first release 2006, last release 2.5.6 May 26, 2011 - No more fix or
update
Python 2.6 first release oct. 2008, last release 2.6.6 April 10, 2012 security
and bug fix until october 2013
- features : prepare migration to Pyton 3.0+
Python 2.7 first relaese
#1903: r.watershed fails with Subprocess failed with exit code 6
-+--
Reporter: marcosc | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal
You can always use shell. But this is a question about 1) the graphical
interface, and 2) python libraries for advanced commands and use in scripting.
Michael
C. Michael Barton
Director, Center for Social Dynamics Complexity
Professor of Anthropology, School of Human
Nikos Alexandris:
I feel that trac makes it difficult (for me) to write and structure the
text for a ticket. I am forced to manually enter [[BR]] to break
lines!
Markus Neteler:
Please don't... it becomes really unreadable.
...
Nikos A:
Indeed, but I still don't find it very
#1903: r.watershed fails with Subprocess failed with exit code 6
-+--
Reporter: marcosc | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal
#1866: broken db driver communication in winGRASS 7
--+-
Reporter: martinl | Owner: grass-dev@…
Type: defect| Status: new
Priority: blocker
Maybe, it is time to some markup support overview...
On 20 March 2013 20:31, Vaclav Petras wenzesl...@gmail.com wrote:
On 20 March 2013 18:33, Nikos Alexandris n...@nikosalexandris.net wrote:
Sure, but why I see for example the supposed list build with a * in front of
each line not being a
On Wed, Mar 20, 2013 at 5:40 PM, Robert Lagacé
robert.lag...@fsaa.ulaval.ca wrote:
Some information :
Python 2.5 first release 2006, last release 2.5.6 May 26, 2011 - No more fix
or update
Python 2.6 first release oct. 2008, last release 2.6.6 April 10, 2012
security and bug fix until
On Wednesday 20 of March 2013 15:00:23 Johannes Radinger wrote:
Hi,
I just wanted to ask how the quiet-flag is defined. I mean, what
will be still reported to the screen (console)? How is it with
self-written e.g. add-ons
in python. If quiet is set are all grass output messages
#1866: broken db driver communication in winGRASS 7
--+-
Reporter: martinl | Owner: grass-dev@…
Type: defect| Status: new
Priority: blocker
StackExchange uses Markdown, by the way ;-)
Your thoughts are 100% valid. We must remember that programmers
usually (or ideally?) use several languages, so using several markups
is natural, too. However, for non-programmers (users) it is usual to
know zero or one markup language because they
#1866: broken db driver communication in winGRASS 7
--+-
Reporter: martinl | Owner: grass-dev@…
Type: defect| Status: new
Priority: blocker
38 matches
Mail list logo
