[GRASS-dev] test scripts in the path

[Vaclav Petras]

On Wed, Nov 26, 2014 at 11:07 AM, Martin Landa <landa.martin at gmail.com>
wrote:

> Hi,
>
> is it need to have such script in the path?
>
> test.r3flow        test.raster3d.lib
>
>
Honestly, I don't know.

This is one of the issues why I'm hesitating to backport the testing. I'm
not sure how much this was discussed on mailing list so far; we had some
discussions with Soeren; there should be something on the GSoC wiki (search
e.g. for MS Windows):

http://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS
http://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS#TestingonMSWindows

The main problem is that these are not scripts but binaries, so you need to
get them compiled somehow. This could be (relatively) easy on Linux but
impossible for users on MS Windows.

Vaclav

Martin
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.eu/mentors/landa
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20141126/1a0cf301/attachment.html>