Re: Fwd: [CMake] CMake 2.8.0 RC 4 ready for testing!

2009-11-03 Thread Brad King
Alexander Neundorf wrote:
 On Tuesday 03 November 2009, David Faure wrote:
 Oh wow, that rocks.
 OK, the benefits clearly outweight the formatting change.
 
 Maybe the addfitional output could be skipped if ctest is run without -j ?

At first I found the Start lines strange too, but after just
a few days I got used to them.  When running ctest -j 8
it feels much more responsive to see the Start lines pop up
right away instead of waiting for tests to finish.

The current behavior resulted after a long internal discussion
during which many alternatives like the above were covered.
I'd rather not repeat the whole thing here.  The summary is that
any alternative to the current behavior requires extra code paths
which we do not want to implement or maintain.  Eventually we'll
have the interactive tty approach I described, and the problem
will go away.

-Brad
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


Re: Fwd: [CMake] CMake 2.8.0 RC 4 ready for testing!

2009-11-02 Thread Brad King
David Faure wrote:
 On Thursday 29 October 2009, Alexander Neundorf wrote:
 Hi,

 please give this RC4 of CMake 2.8.0 try, it is getting close to the final
 2.8.0.
 
 OK, I switched to CMake-2-8 cvs branch today.
 Everything seems to go smoothly, no problems.

Great, thanks for trying it.

 Just one cosmetic remark: why does the output of `make test` now look like 
 this?
 
   Start  1: klocaletest   
 
  1/46 Test  #1: klocaletest ..   Passed0.08 sec   
 
   Start  2: klocalizedstringtest  
 
  2/46 Test  #2: klocalizedstringtest .   Passed0.03 sec   
 
   Start  3: kstandarddirstest 
 
  3/46 Test  #3: kstandarddirstest    Passed0.09 sec   
 
   Start  4: kaboutdatatest
 
  4/46 Test  #4: kaboutdatatest ...   Passed0.02 sec   
 
   Start  5: kurltest  
 
  5/46 Test  #5: kurltest .***Failed0.03 sec  
 [...]
 
 I think this makes it harder to read (twice longer, with one line out of two
 saying nothing really interesting; the Start N: footest line seems useless).

This is because we now support parallel testing: ctest -j 8

The problem is that we do not know the order in which tests will
start or end.  No partial lines can be printed.  Originally we
just printed output only when tests ended.  However, that leaves
no indication of what tests are currently running.  If the first
tests are long, there is no indication anything happens.

In the future, we plan to solve this problem by detecting whether
the output pipe is a tty.  If not, then we can just write the
ending lines and no start lines.  If it is a tty then we can use
escape sequences to keep pending tests listed on the bottom as
each test finishes and a new one starts.  All of this requires
quite a bit of work to do cross-platform, so for now we just went
with the starting lines.  We purposely arranged the columns so
that the most important information on the ending lines sticks
out.

-Brad
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


Fwd: [CMake] CMake 2.8.0 RC 4 ready for testing!

2009-10-29 Thread Alexander Neundorf
Hi, 

please give this RC4 of CMake 2.8.0 try, it is getting close to the final 
2.8.0.

Alex


--  Forwarded Message  --

Subject: [CMake]  CMake 2.8.0 RC 4 ready for testing!
Date: Wednesday 28 October 2009
From: Bill Hoffman bill.hoff...@kitware.com
To: CMake cm...@cmake.org

CMake 2.8.0 RC 4 is now ready for people to try.
You can find the source and binaries here: http://www.cmake.org/files/v2.8/.

Here are the changes for the 2.8.0 branch so far:
Changes in CMake 2.8.0 RC 4
- Fix try_compile when file cannot be found
- Add new module to test manifest installation issues on windows.
- Add more test coverage
- Improvements in finding MPI on windows. ENH: reorganized searching mpi 
for mpi components (include,lib,bin) using a single set of search paths 
instead of seperately mainted lists of paths for each.
- Look for nvcc in the 32 bit bin directory before the 64 bin directory.
- BUG: hardcord some values so output matches cmVS10CLFlagTable.h 
(addresses bug #9753)
- Avoid Intel linker crash in BuildDepends test
- Fix Intel Fortran SHARED libraries on Linux
- Fix working dir issue for ctest
- Fix if() command and CMP0012 OLD/NEW behavior
- Allow for /D to change install directory on the command line for NSIS
- Move SetErrorMode around calls to generate and configure instead of 
setting it for the whole application for cmake-gui on windows.  Allows 
for bad installs of windows shell programs to not break file completion.
- Fix Intel and MinGW Fortran DLL import libraries
- Fix Xcode dylib version default
- Fix the showing of non-cpp files in the IDE for VS 10
- Fix optionally-valued booleans in VS 10 flag table
- Detect and set Unicode character set in VS 10
- Add support for the g95 Fortran compiler
- Test all target types in Fortran
- Add Xcode file association for Fortran
- Fix VS 10 flag table for precompiled headers
- Fix VS 10 .sln files for Windows Explorer
- Fix Microsoft.Cpp.$(Platform).user.props in VS10b2
- Fix up file(DOWNLOAD ) a bit, better error checking and uses of long 
not double for timeout as curl needs, bug# 9748
- Add a VS 10 Win64 generator
- Fix for bug#9686 convert java_home to a cmake path before using.
- fix for bug# 9751, add check for MSVC10
- Fix for bugs #9756, #9690 and #9755, header files were not included, 
and link_directories we incorrect
- Add a module to test an install tree to verify that the MS CRT version 
is correct (cmake -P CMakeVerifyManifest.cmake)
- Fix seg fault for empty ENV{} call bug #9747
- Better fix for finding the MSBuild that matches the VS 10 install.
- make testing the CodeBlocks and Eclipse generators easier by not 
requiring the CMAKE_EDIT_COMMAND variable
- Do not link library dependencies in VS solutions
- Ctest was broken for subdirs.  Restored working directory state for 
tests so that their executables could be found.
- Fixes version detection using osg/Version on Mac OSX when OSG is 
installed as a framework
- Avoid C++ linker language in VS Fortran project
- Avoid duplicate ZERO_CHECK in VS solutions
- Fixed bug 8319, search for the Python shared library in the standard 
locations.
- Fix bug#9714, should not crash when version file is not where it 
should be...
- Fix ctest output alignment for cases where total tests run is not the 
same width as max test index.
- make it more robust wrt. #9621
- Add another possible error message that curl might emit with an empty 
drop location.
- Fix issue #5668 - use CollapseFullPath when determining if covered 
file is within source or binary tree. Allows gcc/gcov coverage analysis 
using MinGW on Windows.
- CTest-side support for compiler name and compiler version information. 
  Requires CDash update to show on CDash.
- Add a bunch more testing coverage.

Changes in CMake 2.8.0 RC 3
- CTest Added OS Platform (cpu architecture) detection support to
windows system
- Several minor FindBoost changes to address posts on mailing list
- Resolve #9685: Fix include dir to be correct path for gnutils
- Fix color check for dependency scanning
- Remove CMP00015 for now as it breaks more things than it fixes
- Reduce duration of ctest_sleep arguments. Add SmallAndFast project.
Replace kwsys with SmallAndFast to make CTestTest faster. (I will keep
an eye on coverage results after this commit and make sure we still have
equivalent ctest coverage.)
- Do not use -fPIC to link executables
- Split Borland compiler information files
- Trimmed off the newline from sw_vers output on mac, it could cause xml
parsing errors if left in
- Check for openssl-linked option with Qt 4.4+ before making ssl a
dependency.
- Make Complex test of CMakeLib more optional
- Modernize FindVTK module
- Fix find_package() when pkg_DIR is wrong
- Do not collapse path of NOTFOUND values
- More robust implicit link line detection regex
- fix Xcode 30 generator
- Use the correct CMake (the freshly built one) to drive the
CMakeWizardTest.
- Support more special characters in file(STRINGS)
- Log implicit link line detection