[cmake-developers] Perforce patch for CTest 2.8

2013-09-30 Thread Pedro Navarro
Hi all, I've written a patch to add Perforce support for CTest 2.8. Although it still needs a little bit more work (I need to look into what I'm supposed to do with Nightly builds ) it properly notifies CTest of all details about check ins, revision numbers, authors and their E-Mail address (by ma

Re: [cmake-developers] Support for coverage.py coverage on the topic stage

2013-09-30 Thread Bill Hoffman
On 9/30/2013 11:24 AM, Rolf Eike Beer wrote: For all other handlers it may happen that more than one coverage db is found in the build tree and they would both be used. This is really useful, e.g. if you want to have coverage for both C and Python code. This will not work with the BullsEye handl

Re: [cmake-developers] INTERFACE_LIBRARY target type

2013-09-30 Thread Stephen Kelly
Brad King wrote: > On 09/11/2013 04:04 AM, Stephen Kelly wrote: >> I've done this part and merged into next for testing. > > This hunk: > > http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=75dc6423#patch31 > > has caused a Watcom failure since it was added: > > http://open.cdash.org/testDe

Re: [cmake-developers] Support for coverage.py coverage on the topic stage

2013-09-30 Thread Rolf Eike Beer
Am 30.09.2013 16:45, schrieb Bill Hoffman: On 9/28/2013 5:36 AM, Rolf Eike Beer wrote: Break if everything is fine, continue on error or when no files are found? All other handlers support being run in parallel, why not Bullseye? Not really. Return 0 if COVFILE is not set so, no coverage. Re

[cmake-developers] Need HP-UX dashboards for CMake (HP-UX B.11.31)

2013-09-30 Thread Bill Hoffman
Hi all, Does anyone have access to a HP-UX B.11.31 machine that can run nightly CMake dashboards? Thanks. -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -

Re: [cmake-developers] INTERFACE_LIBRARY target type

2013-09-30 Thread Brad King
On 09/11/2013 04:04 AM, Stephen Kelly wrote: > I've done this part and merged into next for testing. This hunk: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=75dc6423#patch31 has caused a Watcom failure since it was added: http://open.cdash.org/testDetails.php?test=208258397&build=30439

Re: [cmake-developers] Support for coverage.py coverage on the topic stage

2013-09-30 Thread Patrick Reynolds
That was very poor word choice on my part. My apologies. I mean to say: "I leave that to someone more expert in the Bullseye system." -- Patrick Reynolds Technical Leader Kitware, Inc. 919 869 8848 On Monday, September 30, 2013 at 10:32 AM, Bill Hoffman wrote: > On 9/29/2013 2:37 PM, Patric

Re: [cmake-developers] Support for coverage.py coverage on the topic stage

2013-09-30 Thread Bill Hoffman
On 9/28/2013 5:36 AM, Rolf Eike Beer wrote: Break if everything is fine, continue on error or when no files are found? All other handlers support being run in parallel, why not Bullseye? Not really. Return 0 if COVFILE is not set so, no coverage. Return 0 if COVFILE is set but there was nothin

Re: [cmake-developers] Support for coverage.py coverage on the topic stage

2013-09-30 Thread Bill Hoffman
On 9/29/2013 2:37 PM, Patrick Reynolds wrote: I'll leave this one to folks who are better versed in the arcane art of Bullseye... Does anyone still use this? ;) Yes, it is still in use, and no it is not arcane. It is a really good commercial cross platform branch based coverage tool. With