1. 15 Dec, 2009 2 commits
  2. 14 Dec, 2009 8 commits
  3. 13 Dec, 2009 1 commit
  4. 12 Dec, 2009 1 commit
  5. 11 Dec, 2009 7 commits
  6. 10 Dec, 2009 13 commits
    • Kitware Robot's avatar
      KWSys Nightly Date Stamp · be12a1ae
      Kitware Robot authored
    • Zach's avatar
      Restore the "***Not Run" message to ctest command line output for tests which... · 5e427677
      Zach authored
      Restore the "***Not Run" message to ctest command line output for tests which did not start due to missing/bad executables or missing required files.
    • Zach's avatar
      Unfortunately, I noticed the comment on bug 8668 too late. This changes my... · 4de7cc36
      Zach authored
      Unfortunately, I noticed the comment on bug 8668 too late.  This changes my last implementation of the exe wrapper to something which makes much more sense: a REQUIRED_FILES property on tests.
    • Zach's avatar
      [0008668: CTest Dev: Missing executables shown as failed tests when using... · 48b61339
      Zach authored
      [0008668: CTest Dev: Missing executables shown as failed tests when using MPI.]  Added a wrapping option to add_test so that exes built by the project can be safely wrapped in other exes and be listed as "not run" rather than "failed" if they are not built.
    • Brad King's avatar
      New decision method to enable Fortran tests · 55275e01
      Brad King authored
      CMake does not enable Fortran for its own build, but it needs to find a
      Fortran compiler to know if it is possible to enable Fortran tests.
      Previously we searched for a hard-coded list of Fortran compilers which
      was duplicated from the CMakeDetermineFortranCompiler.cmake module.  We
      now run CMake on a small test project that enables the Fortran language
      and reports the compiler it found.  This represents a more realistic
      check of whether the Fortran tests will be able to find a compiler.
    • Brad King's avatar
      Always use a configuration for CMake tests · faf6d82b
      Brad King authored
      Previously our EnforceConfig script that loads at test-time would only
      enforce a non-empty CTEST_CONFIGURATION_TYPE for CMake 2.6.2 and lower.
      Now we simply always enforce use of a configuration, and select one of
      the configurations that was built if none is given.
      This is necessary to run tests like CMake.Install that need to know the
      configuration with which CMake was built.
    • Brad King's avatar
      Test 'install' target of CMake itself · 6c79c962
      Brad King authored
      We create option CMake_TEST_INSTALL to enable a new CMake.Install test.
      It tests running the "make install" target to install CMake itself into
      a test directory.  We enable the option by default for dashboard builds.
    • Brad King's avatar
      Apply CMake test-time config to all tests · 9d823f78
      Brad King authored
      We configure an EnforceConfig.cmake script to load at CTest time.
      Previously we loaded it from Tests/CTestTestfile.cmake, but now we load
      it from the top level so it applies to all tests.
    • Zach's avatar
    • Brad King's avatar
      Fix installation of CMake itself · 30f17e29
      Brad King authored
      CMake 2.8.0 and below use the EXECUTABLE_OUTPUT_PATH setting from the
      top-level CMakeLists.txt file to compute the location of the "cmake"
      target for the special case of installing cmake over itself.
      The commit "Clean up CMake build tree 'bin' directory" moved the setting
      of EXECUTABLE_OUTPUT_PATH that affects the "cmake" target into the
      Source subdirectory.  This broke the special-case lookup in the top
      level.  We fix it by setting EXECUTABLE_OUTPUT_PATH at the end of the
      top-level CMakeLists.txt file.  Now that we use add_subdirectory to
      process the subdirectories in order, this setting does not affect the
      subdirectories.  Thus we fix installation while preserving the clean
      build tree 'bin' directory intended by the above-mentioned commit.
    • Brad King's avatar
      Use add_subdirectory instead of subdirs in CMake · 31e26820
      Brad King authored
      We switch CMake's own top-level CMakeLists.txt file to use the modern
      add_subdirectory() command instead of the old subdirs() command.  This
      enables in-order processing.
    • Brad King's avatar
      Simplify CMake self-install special case · d5eb99cb
      Brad King authored
      CMake has a special case for the "make install" target when building
      CMake itself.  We use the just-built CMake to install itself since an
      existing CMake installation cannot replace itself (at least on Windows).
      We simplify the code that computes the location of the CMake binary by
      taking advantage of existing generator support for target lookup.  This
      will make it robust to any changes in CMake's own CMakeLists.txt files
      in the future.
    • Clinton Stimpson's avatar
      BUG: Fix bug #10,000. · 419d050b
      Clinton Stimpson authored
      Some fixes for including Qt frameworks.
      Remove extra "QtGui.framework" so its not Contents/Frameworks/QtGui.framework/QtGui.framwork/... anymore.
      Also include QtGui Resource folder, so a Cocoa/Qt based cmake-gui app works.
  7. 09 Dec, 2009 4 commits
  8. 08 Dec, 2009 4 commits
    • Kitware Robot's avatar
      KWSys Nightly Date Stamp · 02a8eee3
      Kitware Robot authored
    • Brad King's avatar
      Test XML encoding with UTF-8 character validation · f5ac85a2
      Brad King authored
      This creates a unit test for cmXMLSafe.  See issue #10003.
    • Brad King's avatar
      Test UTF-8 decoding · 0a64936f
      Brad King authored
      This creates a unit test for cm_utf8.  See issue #10003.
    • Brad King's avatar
      CTest: Do not munge UTF-8 output in XML files · e4beefeb
      Brad King authored
      CTest filters the output from tools and tests to ensure that the XML
      build/test result documents it generates have valid characters.
      Previously we just converted all non-ASCII bytes into XML-escaped
      Unicode characters of the corresponding index.  This does not preserve
      tool output encoded in UTF-8.
      We now assume UTF-8 output from tools and implement decoding as
      specified in RFC 3629.  Valid characters are preserved, possibly with
      XML escaping.  Invalid byte sequences and characters are converted to
      human-readable hex values with distinguishing tags.  See issue #10003.