*** empty log message ***

diff --git a/ctest/README.txt b/ctest/README.txt
index 8b446080f47aeb95cb9e9a8132980e60b65b8358..d788f87912c335f0ee9f72c2c8c9a6fd19c54dfd 100644 (file)
--- a/ctest/README.txt
+++ b/ctest/README.txt
@@ -12,7 +12,8 @@ of the 'creatools', test it and submit results to creatis dashboard.
    in your ctest file (see below)
 
 2) Copy the ctest file corresponding to your os in the test dir,
-   e.g. copy 'creatools-linux.ctest' if you are on a linux platform.
+   e.g. copy 'creatools-linux-osx.ctest' if you are on a linux 
+   or on a mac osx platform.
 
 3) Edit the copied file and make the necessary changes inside 
    following the comments therein. 
@@ -33,7 +34,7 @@ of the 'creatools', test it and submit results to creatis dashboard.
 5) To run a test, type in test dir:
    'ctest -S creatools-OS.ctest,PROJECTNAME' [-V|-VV]
    Where : * 'creatools-OS.ctest' is the name of your customized ctest file,
-          (OS is your OS type)
+          (e.g. creatools-linux-osx.ctest)
           * PROJECTNAME is the name of the project to build and test
           (e.g. crea, bbtk, ...)
           * add -V or -VV tu run in verbose or extra-verbose mode
@@ -53,6 +54,8 @@ A consistent build order is:
 - creaMaracasVisu (depends on crea, bbtk)
 - creaContours (depends on crea, bbtk, creaImageIO, creaEnvironment, creaMaracasVisu)
 
+On linux or osx, see the bash script ctest-all-creatools.sh
+
 ----------------
 REM: To schedule automatic build, see :
   http://www.vtk.org/Wiki/CMake_Scripting_Of_CTest

diff --git a/ctest/ctest-all-creatools.sh b/ctest/ctest-all-creatools.sh
new file mode 100755 (executable)
index 0000000..facb75e
--- /dev/null
+++ b/ctest/ctest-all-creatools.sh
@@ -0,0 +1,8 @@
+#!/bin/bash
+source ~/.bashrc
+ctest -S creatools-linux.ctest,crea -V
+ctest -S creatools-linux.ctest,bbtk -V
+ctest -S creatools-linux.ctest,creaImageIO -V
+#ctest -S creatools-linux.ctest,creaEnvironment -V
+#ctest -S creatools-linux.ctest,creaMaracasVisu -V
+#ctest -S creatools-linux.ctest,creaContours -V