On Thu, Apr 28, 2011 at 12:49 AM, <mika.raj...@patria.fi> wrote: > Hi > > Another update and a question > > I'v reverse engineered and hacked the CDash/CMake/CTest code a bit to see > how it works. > > I'v now come to the conclusion that the best way to handle custom tools > (style checks, static code analysis) is to use custom builds and custom > build groups > > The issue I currently have is this: > > How to generate a custom "Build.xml" file for CDash, based on output of a > program? > > The extreme solution I see is to make my own executable that generates a > "Build.xml" file as output. > > What I'd like to do is to tell CTest to pick up errors / warnings from > line that match with a regular expression i give. > > What would be the best way to do this? >
Search for information on using a CTestCustom.cmake file to match custom warning or error output. ( My blog post on a related subject: http://www.kitware.com/blog/home/post/27 ) > -mika > > > > > From: mika.raj...@patria.fi > To: mika.raj...@patria.fi > Cc: cmake@cmake.org, cmake-boun...@cmake.org > Date: 21.04.2011 09:54 > Subject: Re: [CMake] CDash Dynamic Analysis > Sent by: cmake-boun...@cmake.org > ------------------------------ > > > > Hi > > I went for the custom DynamicAnalysis.xml thing > > I think I figured out what the file should contain. > > There is a slight problem however. > > The Labels in the defect list of CDash are that of some other tool > > How do I change them? > > -mika > > > > From: mika.raj...@patria.fi > To: mika.raj...@patria.fi > Cc: cmake@cmake.org, cmake-boun...@cmake.org > Date: 15.04.2011 15:47 > Subject: Re: [CMake] CDash Dynamic Analysis > Sent by: cmake-boun...@cmake.org > ------------------------------ > > > > Hi > > This doesn't seem to be very easy, fun or well documented. > > I'v resolved to looking aroung the CTest source code to see what is going > on. > > From what I'v found out, there seems to be some syntax to what the defect > list contains! > > <DefectList> > <Defect Type="mysteryXXXX"/> > <DefectList> > > I'm not certain if this is the easy way through, but it's the only way i > see possible at the moment. > > I think i need to create my own program which eats program output and poops > DynamicAnalysis.xml files. > > Perhaps i'll even add some way of configuration to it. > > -mika > > > > From: mika.raj...@patria.fi > To: cmake@cmake.org > Date: 14.04.2011 09:11 > Subject: [CMake] CDash Dynamic Analysis > Sent by: cmake-boun...@cmake.org > ------------------------------ > > > > Hi > > I'm trying to integrate custom tools to CDash Dynamic analysis. > > I'm not that certain on what is the way I should be going. > > Is there a way to tell cmake to pick up lines from a program as defects in > the custom tool submission xml? > > Do i need to make a program that generates a valid xml file? > > If so, where do I find the documentation on how to do it? > > I downloaded the example XML files from *http://www.itk.org/Wiki/CDash:XML > * <http://www.itk.org/Wiki/CDash:XML> > > here is a part of it > > <Results /> > <Log /> > </Test> > <DefectList /> > <EndDateTime>Sep 15 19:36 CEST</EndDateTime> > <ElapsedMinutes>644.3</ElapsedMinutes> > </DynamicAnalysis> > </Site> > > I think that I should modify the part "DefectList". > But this file doesn't give much information on what to do. > > There was a XML Schema file as well, but it wasn't of much use. > > </xs:element> > <xs:element name="DefectList" type="xs:string" minOccurs="0" /> > <xs:element name="EndDateTime" type="xs:string" minOccurs="0" /> > <xs:element name="ElapsedMinutes" type="xs:float" minOccurs="0" /> > </xs:sequence> > > -mika_______________________________________________ > Powered by *www.kitware.com* <http://www.kitware.com> > > Visit other Kitware open-source projects at * > http://www.kitware.com/opensource/opensource.html*<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* <http://www.cmake.org/Wiki/CMake_FAQ> > > Follow this link to subscribe/unsubscribe:* > **http://www.cmake.org/mailman/listinfo/cmake*<http://www.cmake.org/mailman/listinfo/cmake> > _______________________________________________ > Powered by *www.kitware.com* <http://www.kitware.com> > > Visit other Kitware open-source projects at * > http://www.kitware.com/opensource/opensource.html*<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* <http://www.cmake.org/Wiki/CMake_FAQ> > > Follow this link to subscribe/unsubscribe:* > * > *http://www.cmake.org/mailman/listinfo/cmake*<http://www.cmake.org/mailman/listinfo/cmake> > _______________________________________________ > 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 > > _______________________________________________ > 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 >
_______________________________________________ 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
