Hi,
is it need to have such script in the path?
test.r3flow test.raster3d.lib
Martin
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.eu/mentors/landa
On Wed, Nov 26, 2014 at 11:07 AM, Martin Landa <landa.martin@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@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
These are binaries and needed for testing purposes. They are called by
gunittest Python scripts, so they need to be in the module path. They
are build by default, but surely can be removed from Windows or Linux
package/distributions.
An other approach would be to add test build to the Makefile system,
so that "make test" will build all test binaries? But i have no time
to integrate such an approach.
Best regards
Soeren
2014-11-26 17:07 GMT+01:00 Martin Landa <landa.martin@gmail.com>:
Hi,
is it need to have such script in the path?
test.r3flow test.raster3d.lib
Martin
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.eu/mentors/landa
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev