2011/2/23 Eric Noulard <[email protected]>: > 2011/2/23 Clinton Stimpson <[email protected]>: > >> I've having problems with these tests too. >> If they fail once, they will keep failing until some files generated by the >> failed test are cleaned up. > > Some files should be, the package files located at the root of the build dir. > >> Seems to me that an extra cleanup step should be done before or during the >> "ctest --build-and-test ...." for these tests that glob for generated files. >> Could you do this with a ctest script that cleans the test specific build >> directory before doing the configure/build/test? And call that ctest script >> in the add_test() call? >> I'm not sure if this is a good idea, but what if the glob was done under the >> _CPack_Packages directory which cpack always cleans beforehand. > > In my case it wouldn't be enough to kill _CPack_Packages there will remain > spurious files in the build tree.
I did pushed forward the CPack-ChangeComponentNamingScheme branch the test itself is cleaning up the build tree from expected package files before running CPack. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org _______________________________________________ cmake-developers mailing list [email protected] http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
