Re: [GRASS-dev] v.mapcalc missing UI

Martin Landa wrote: > does anyone know how v.mapcalc should work? It seems to me that the > module lacks an UI, no options, no G_parser(). It leads to the fact > that > > v.mapcalc --help > > just freezes. v.mapcalc reads the expression from stdin (see yylex.c); argv is ignored. Not only

Re: [GRASS-dev] Failing tests overview for September 2015

On Sat, Oct 3, 2015 at 6:40 PM, Vaclav Petras wrote: ... > Seems like the NC basic dataset has different column types then full NC. > Needs further investigation. BTW, what about Datasets category for Trac? Done. Markus ___

[GRASS-dev] v.mapcalc missing UI

Hi, does anyone know how v.mapcalc should work? It seems to me that the module lacks an UI, no options, no G_parser(). It leads to the fact that v.mapcalc --help just freezes. I blacklisted this module in r66406 from addons generation. It means that this module lacks its description in

Re: [GRASS-dev] v.mapcalc missing UI

On Sun, Oct 4, 2015 at 11:53 AM, Martin Landa wrote: > Hi, > > does anyone know how v.mapcalc should work? It seems to me that the > module lacks an UI, no options, no G_parser(). It leads to the fact > that > > v.mapcalc --help > > just freezes. I blacklisted this module

[GRASS-dev] wx.metadata installation issues & pygrass set_path() question

Hi all, when trying to fix all compilation and installation issues I replaced get_lib_path() by set_path() [1]. These functions are not used in GRASS core codebase. Their usage is not clear to me. Fn get_lib_path() says "Return the path of the libname contained in the module". So I would expect

Re: [GRASS-dev] compile errors when using stripped-down config

On Sat, Oct 3, 2015 at 3:46 AM, Maris Nartiss wrote: > Hello, > some of GRASS compilation "options" are not optional at all - > resulting outcome even if will work, will be useless for endusers. > Don't try to push everything into use flags. That's not really my

Re: [GRASS-dev] wx.metadata installation issues & pygrass set_path() question

On Sun, Oct 4, 2015 at 8:30 AM, Martin Landa wrote: > when trying to fix all compilation and installation issues I replaced > get_lib_path() by set_path() [1]. These functions are not used in > GRASS core codebase. Their usage is not clear to me. The replacement was

Re: [GRASS-dev] [GRASS-SVN] r66413 - grass-addons/grass7/vector/v.kriging

On Sun, Oct 4, 2015 at 9:08 AM, wrote: > > Author: neteler > Date: 2015-10-04 06:08:45 -0700 (Sun, 04 Oct 2015) > New Revision: 66413 > > Modified: >grass-addons/grass7/vector/v.kriging/local_proto.h > Log: > v.kriging: add missing la.h header > > @@ -13,6 +13,7 @@ >

Re: [GRASS-dev] wx.metadata installation issues & pygrass set_path() question

Hi Martin, On Sun, Oct 4, 2015 at 2:30 PM, Martin Landa wrote: > Hi all, > > when trying to fix all compilation and installation issues I replaced > get_lib_path() by set_path() [1]. These functions are not used in > GRASS core codebase. Their usage is not clear to me.