The article I referred to earlier in this thread is now available electronically in the pdf downloadable from here: http://www.kitware.com/products/thesource/july2009.html
It's about using subprojects for your project in terms of its CDash dashboard and in terms of its CMake-based build system. The article appears on pp. 10 - 13 of The Source newsletter, July 2009. Subscribers will receive their printed copies within the next couple of weeks. A grep in the CMake code base for "SubProject" "LABELS" and "CTEST_USE_LAUNCHERS" reveals source level information. CTEST_USE_LAUNCHERS is required to classify build errors and warnings according to their target/source files LABELS properties. If not used, no big deal, the build errors and warnings will just not have the same set of LABELS associated with them. CTEST_USE_LAUNCHERS only currently makes sense with makefile based builds (not Visual Studio or Xcode) using CVS CMake -- we are planning on figuring out a way to make them useful via Visual Studio or at least to retrieve the same information from the build logs. Stay tuned... More documentation to come... HTH, David On Tue, Jul 21, 2009 at 12:32 PM, Mathieu Malaterre < [email protected]> wrote: > It would be nice just to have at least a keyword to grep cmake source > code with... > I am also looking for configuring my subproject and cannot find > anything in cmake or cdash documentation... > > thanks, > > On Thu, Jul 16, 2009 at 7:26 PM, David Cole<[email protected]> wrote: > > I've written an article which will appear in the upcoming issue of the > > Kitware Source newsletter. I will reply again with a link when the > > newsletter is published. Should be within the next two weeks or so. > > > > > > David Cole > > > > On Thu, Jul 16, 2009 at 11:26 AM, Nathaniel Waisbrot (Cont ARL/CISD) > > <[email protected]> wrote: > >> > >> I'd like to set up CDash to use sub-projects, as seen here: > >> > >> http://trilinos-dev.sandia.gov/cdash/index.php?project=Trilinos > >> > >> On the Trilinos dashboard, multiple smaller projects' results are > >> reported and then aggregated into the top-level "Trilinos" project. > >> > >> > >> I'm having trouble finding any documentation on how to do the > >> configuration, though. My dashboard submissions end up going to the > >> top-level project instead of the subordinates. > >> > >> I'd like the sub-projects to be able to run independently. So, for > >> example, someone could build "xframework" one day with 1 error, and > >> someone else "Qt" the next day with 2 errors, and the dashboard would > >> show the "CSE" super-project with 3 errors in total. > >> > >> Is this possible? Anyone able to offer some instructions? > >> > >> > >> > >> -- > >> Nathaniel Waisbrot > >> Software Dev Analyst > >> Lockheed Martin / ARL DoD Supercomputing Resource Center > >> Adelphi Laboratory Center, MD 20783 > >> Phone: 301-394-0096 > >> Email: [email protected] > >> > >> _______________________________________________ > >> Cdash mailing list > >> [email protected] > >> http://public.kitware.com/cgi-bin/mailman/listinfo/cdash > > > > > > _______________________________________________ > > Cdash mailing list > > [email protected] > > http://public.kitware.com/cgi-bin/mailman/listinfo/cdash > > > > > > > > -- > Mathieu >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
