On Thu, Jun 11, 2009 at 5:50 AM, Brad King<brad.k...@kitware.com> wrote: > Instead we should have one add_custom_target() to do all the tests > for a single library (e.g. function). Within the target there would > be file-level rules created by add_custom_command(). This will > translate to one .vcproj file per library that contains a bunch of > rules to drive the tests (with proper dependencies).
FWIW, I put in a hack for this already. The "libname-test" target depends on all of the test binaries for the library libname, then runs CTest with the appropriate regex for that library. It would be relatively easy to build a "libname-test-with-deps" target for each library that also tests libraries depending (directly or indirectly) on the library libname. We have all of the dependency information already. - Doug _______________________________________________ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
