[Plplot-cvs] SF.net SVN: plplot:[9328] trunk/README.testing

[<ai...@us...>]

Revision: 9328
          http://plplot.svn.sourceforge.net/plplot/?rev=9328&view=rev
Author:   airwin
Date:     2009-01-17 05:57:35 +0000 (Sat, 17 Jan 2009)

Log Message:
-----------
Insert remarks about locale issues.

Modified Paths:
--------------
    trunk/README.testing

Modified: trunk/README.testing
===================================================================
--- trunk/README.testing	2009-01-16 20:09:51 UTC (rev 9327)
+++ trunk/README.testing	2009-01-17 05:57:35 UTC (rev 9328)
@@ -1,6 +1,6 @@
 The definitive set of instructions is given at
 http://www.miscdebris.net/plplot_wiki/index.php?title=Testing_PLplot.  The
-material below is cut and pasted from there as of 2009-01-10.
+material below is cut and pasted from there as of 2009-01-16.
 
 Testing PLplot
 ==============
@@ -24,13 +24,18 @@
 The last test run by ctest is a comparison of PostScript (-dev psc) results
 and stdout from each language interface to PLplot with the corresponding
 results for C. In general, these results are identical which is a stringent
-test of our language bindings. Test the results not generated by -dev psc by
-viewing them with a viewer appropriate for each particular file type that is
-generated. Note, these tests of the PLplot build can only be performed if
-cmake is invoked with the -DBUILD_TEST=ON option (which roughly doubles the
-build time because all the examples must be built). 
+test of our language bindings.  (Note it is the user's responsibility
+to insure the locales are consistent for all languages since inconsistent
+locales can produce inconsistent stdout results which have nothing to
+do with PLplot bindings or examples issues.)
 
+Test the results not generated by -dev psc by viewing them with a viewer
+appropriate for each particular file type that is generated. Note, these
+tests of the PLplot build can only be performed if cmake is invoked with the
+-DBUILD_TEST=ON option (which roughly doubles the build time because all the
+examples must be built). 
 
+
 Install tree tests 
 ------------------
 
@@ -49,8 +54,10 @@
 effect of the above "cp" and "cd" commands is to copy the examples subtree
 of the install tree to /tmp and build and test the examples in the copied
 subtree to keep a clean install tree. However, an alternative is to replace
-those two commands with cd $prefix/share/plplot$plplot_version/examples
+those two commands with 
 
+cd $prefix/share/plplot$plplot_version/examples
+
 and build and test the install-tree examples right in the examples subtree
 of the install tree with the above "make" commands. 
 
@@ -62,12 +69,12 @@
 PLplot version as ctest does for the build-tree version of PLplot so the
 same remarks hold about the comprehensive nature of the test, the size (2GB)
 of the files produced, the comparison of results for various language
-interfaces with the C result for -dev psc, and testing non-psc results using
-the viewer appropriate for the format. Although the tests are the same, the
-Makefile implementation is different from the ctest implementation in the
-build tree so that in particular you can do these install tree tests in
-parallel using the (GNU-)make -j option to greatly speed up these tests on a
-multi-processor computer. 
+interfaces with the C result for -dev psc, locale issues, and testing
+non-psc results using the viewer appropriate for the format. Although the
+tests are the same, the Makefile implementation is different from the ctest
+implementation in the build tree so that in particular you can do these
+install tree tests in parallel using the (GNU-)make -j option to greatly
+speed up these tests on a multi-processor computer. 
 
 N.B. the above "make test_interactive" command executes our interactive
 examples. There is currently no counterpart for this test in the build tree.


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.