From: Kris T. <kri...@cs...> - 2005-07-19 10:02:40
|
Hi When I try to run "make test" or "ctest" in any of my build directories, I get messages like: 1/277 Testing vcl_test_algorithm Unable to find executable: vcl_test_all ... The following tests FAILED: 1 - vcl_test_algorithm (Not Run) All executables are built though in my target directory, but somehow ctest doesn't find any of them. I wonder if this is because on CYGWIN, the executable is called vcl_test_all.exe, but actually I have no clue... (I'm a bit confused by cmake and ctest). On the other hand netlib/tests/Makefile does seem to be ok: TARGETS = \ /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_integral_test.exe \ /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_lbfgs_example.exe \ /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_lsqr_test.exe \ /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_slamch_test.exe \ /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_tricall.exe I've extracted vxl from cvs yesterday, am using latest CYGWIN on Windows XP Home sp2, gcc -v reports gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125). My processor is a Pentium 4 2.93GHz. cmake version 2.0.6 ctest version 2.0.6 Many thanks Kris Thielemans Hammersmith Imanet, part of GE Healthcare Cyclotron Building Hammersmith Hospital Du Cane Road London W12 ONN, United Kingdom web site address: http://www.hammersmithimanet.com/~kris ------------------------------------------- NOTE: My inbox has a SPAM filter that automatically throws away suspect messages. If you expect a reply and don't get one, your message might have been wrongly classified. |
From: Ian S. <ian...@st...> - 2005-07-19 12:50:16
|
Kris Thielemans wrote: > Hi > > When I try to run "make test" or "ctest" in any of my build directories, I > get messages like: > 1/277 Testing vcl_test_algorithm Unable to find executable: > vcl_test_all > ... > The following tests FAILED: > 1 - vcl_test_algorithm (Not Run) > > All executables are built though in my target directory, but somehow ctest > doesn't find any of them. I wonder if this is because on CYGWIN, the > executable is called vcl_test_all.exe, but actually I have no clue... (I'm a > bit confused by cmake and ctest). On the other hand netlib/tests/Makefile > does seem to be ok: > TARGETS = \ > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_integral_test.exe \ > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_lbfgs_example.exe \ > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_lsqr_test.exe \ > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_slamch_test.exe \ > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_tricall.exe I'd guess that either 1. You haven't turned on the building of the tests. Check BUILD_TESTING is "ON" in CMake. or 2. your build hasn't worked. Check you build didn't report any errors. vcl_test_all should be in $VXLBIN/vcl/tests or if you have modified CMake's EXECUTABLE_OUTPUT_PATH variable, they'll be in there. Ian. |
From: Kris T. <kri...@cs...> - 2005-07-19 13:00:33
|
Hi Ian My CmakeCache.txt does contain BUILD_TESTING:BOOL=ON Just to be clear, make does build the test executables (so vcl_test_all.exe is in EXECUTABLE_OUTPUT_PATH). However, ctest cannot execute the tests. (I have no idea what ctest needs, but I assumed it was the TRAGETS variablem which looks ok). Maybe this is also a question for the cmake list Thanks Kris > > > > When I try to run "make test" or "ctest" in any of my build > > directories, I get messages like: > > 1/277 Testing vcl_test_algorithm Unable to > find executable: > > vcl_test_all > > ... > > The following tests FAILED: > > 1 - vcl_test_algorithm (Not Run) > > > > All executables are built though in my target directory, > but somehow > > ctest doesn't find any of them. I wonder if this is because > on CYGWIN, > > the executable is called vcl_test_all.exe, but actually I have no > > clue... (I'm a bit confused by cmake and ctest). On the other hand > > netlib/tests/Makefile does seem to be ok: > > TARGETS = \ > > > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_integral_test.exe \ > > > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_lbfgs_example.exe \ > > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_lsqr_test.exe \ > > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_slamch_test.exe \ > > /home/kris/MyDocuments/devel/vxlbuild/bin/netlib_tricall.exe > > I'd guess that either > 1. You haven't turned on the building of the tests. > Check BUILD_TESTING is "ON" in CMake. > or > 2. your build hasn't worked. > Check you build didn't report any errors. > vcl_test_all should be in $VXLBIN/vcl/tests > or if you have modified CMake's > EXECUTABLE_OUTPUT_PATH variable, > they'll be in there. > > Ian. > |
From: Ian S. <ian...@st...> - 2005-07-19 13:09:35
|
Kris Thielemans wrote: > > Hi Ian > > My CmakeCache.txt does contain > BUILD_TESTING:BOOL=ON > > Just to be clear, make does build the test executables (so vcl_test_all.exe > is in EXECUTABLE_OUTPUT_PATH). Try setting EXECUTABLE_OUTPUT_PATH to empty - which is the default value that most people use. |
From: Kris T. <kri...@cs...> - 2005-07-19 20:24:31
|
> > Try setting EXECUTABLE_OUTPUT_PATH to empty - which is the > default value that most people use. > Yes! That did work then. I guess I'll send this to the cmake list. Thanks Ian! (By the way, after manually editing v3p/netlib/Makefile to replace -O3 with -O2, all tests worked) Kris |
From: William A. H. <bil...@ny...> - 2005-07-20 13:53:51
|
The fix should be in vxl, here is what itk does: SET(CXX_TEST_PATH ${EXECUTABLE_OUTPUT_PATH}) # set in top level cmakelist file # all tests are prefixed with the path: ADD_TEST(itkAnnulusOperatorTest ${CXX_TEST_PATH}/itkCommonTests itkAnnulusOperatorTest) -Bill At 04:24 PM 7/19/2005, Kris Thielemans wrote: > >> >> Try setting EXECUTABLE_OUTPUT_PATH to empty - which is the >> default value that most people use. >> > >Yes! That did work then. I guess I'll send this to the cmake list. > >Thanks Ian! > >(By the way, after manually editing v3p/netlib/Makefile to replace -O3 with >-O2, all tests worked) > >Kris > > > >------------------------------------------------------- >SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >from IBM. Find simple to follow Roadmaps, straightforward articles, >informative Webcasts and more! Get everything you need to get up to >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >_______________________________________________ >Vxl-users mailing list >Vxl...@li... >https://lists.sourceforge.net/lists/listinfo/vxl-users |
From: Stefan v. W. <svw...@mn...> - 2005-10-19 18:24:47
|
What is the recommended procedure to compile vxl (1.3.0) on Windows using the cygwin (without need for the cygwin1.dll) or mingw tools? I started with cygwin and the -mno-cygwin flag in CXX_FLAGS and CC_FLAGS. This brought me to some errors e.g.: /cygdrive/g/src/vxl/vxl-1.3.0/core/vnl/vnl_sample.cxx: In function `void vnl_sample_reseed()': /cygdrive/g/src/vxl/vxl-1.3.0/core/vnl/vnl_sample.cxx:28: error: `srand48' undeclared (first use this function) I think this is because there are different stdlib.h files in /usr/include and /usr/include/mingw . It looks like cmake doesn't use the /usr/include/mingw/stdlib.h The were other problems with pthread.h not found. Then I switched to a pure mingw environment. But there I couldn't build cmake. Using the cygwin ccmake brought an error with strstream.h not found. Please tell me what configurations are working for you. Thanks a lot, Stefan v. Wachter ALPHA-OMEGA digital GmbH Munich |