Hi, <br>I have `un explained` behavior of CTest and VS 2003...<br>Let me formulate the problem briefly: <br><br>1. I have a project, consisting of foo.dll and 4 executables, using it; <br>2. the structure of the project is:<br>
root/<br> kernel/bin/Release/foo.dll<br> test1/bin....<br> test2/bin...<br> test3/bin...<br> test4/bin...<br>3. each directory ( root, kernel, test1, test2, test3, and test4) has CMakeLists.txt<br>
CMakeLists.txt within root, has ENABLE_TESTING() statement;<br> Each of kernel, test1, test2, test3, and test4 represents different projects within the solution.<br> CMakeLists.txt within test1...test4 directories, has ADD_TEST() statement, pointing to test1.exe, test2.exe, etc.<br>
<br>4. cmake run with no problem indication; <br><br>5. When VS 2003 is opened, the projects are built with no problem indication. <br><br>So far everything behaved as expected. Now, the `unexplained' started: <br> <br>
u.1. Attempt to build RUN_TESTS project within VS 2003 finishes with message: <br> '' foo.dll not found. ''. At the same time: <br> a. the foo.dll is definitely present within specified directory.<br>
b. execution of test1, test2, test3, or test4 from the same environment is running fine. <br> c. root/kernel/bin/Release is within CTEST_ENVIRONMENT variable; <br><br> u.2 At the same time, running ctest within Windows command line window, within <br>
root/ subdirectory, running fine, executing all 4 simple tests, with no indication of <br> missing foo.dll<br><br> u3. Generating the VS 2005 solution/projects from the same scripts, ends up with expected <br>
behavior. Attempt to build RUN_TESTS project, ends up in execution of 4 tests, with no <br> indication of missing foo.dll<br><br>I hope that I just missed some small detail within invoking CTEST suite... Any help and advice<br>
will be appreciated. <br><br>Have a great day, <br>Michael <br><br>P.S> The above has been done with cmake-2.6.0. exe, different Windows XP installations.<br><br> <br><br><br> <br>