1. 28 Feb, 2012 2 commits
    • Brad King's avatar
      find_package: Test error and warning messages in failure cases · eeaaffcb
      Brad King authored
      Add a "CMakeCommands.find_package" test to run CMake on a bunch of cases
      in which find_package fails.  Check that the process return code and
      warning/error messages are as expected.  Record expected test output in
      corresponding files for reference by the check.  These files will also
      serve as a reference for the message text in each case.
    • Brad King's avatar
      Add infrastructure for CMakeCommands tests · 5e1a5c44
      Brad King authored
      Generalize the build_command test framework as a macro to add the
      test.  Process the CMakeCommands subdirectory explicitly.
  2. 13 Feb, 2012 1 commit
  3. 09 Feb, 2012 6 commits
  4. 08 Feb, 2012 1 commit
    • Brad King's avatar
      Add CheckLanguage module · 5db99e87
      Brad King authored
      Define a "check_language(<lang>)" macro to test whether <lang> can be
      enabled.  Cache the result in CMAKE_<lang>_COMPILER.  Add a test case
      covering expected results.
  5. 03 Feb, 2012 3 commits
    • Brad King's avatar
      Remove unused test code · daa41016
      Brad King authored
      We have not run tests with the "como" compiler or enabled the
      experimental ConvLibrary test for years.
    • Brad King's avatar
      Fix CXX/Fortran MODULE flags when enabled before C (#12929) · 74958450
      Brad King authored
      If CXX or Fortran is enabled before C then the values of
      may not be available.  On platforms where MODULE library (plugin) creation
      is the same as SHARED library creation initialize the MODULE creation
      flags from the SHARED creation flags of the matching language instead of
      assuming that C has been enabled first.
      Teach the COnly and CxxOnly tests to build MODULE libraries.  The latter
      covers this specific case.
    • David Cole's avatar
  6. 01 Feb, 2012 1 commit
  7. 30 Jan, 2012 1 commit
  8. 26 Jan, 2012 3 commits
  9. 25 Jan, 2012 1 commit
  10. 22 Jan, 2012 1 commit
  11. 21 Jan, 2012 1 commit
  12. 20 Jan, 2012 3 commits
  13. 18 Jan, 2012 1 commit
  14. 17 Jan, 2012 2 commits
  15. 16 Jan, 2012 2 commits
  16. 13 Jan, 2012 2 commits
    • Brad King's avatar
      Tolerate cycles in shared library link interfaces (#12647) · 8e756d2b
      Brad King authored
      Since commit 183b9509 (Follow all dependencies of shared library private
      dependencies, 2011-12-14) we honor LINK_INTERFACE_LIBRARIES when
      following dependent shared libraries.  The link interface properties may
      form a cycle if set incorrectly by a project.  Furthermore, the property
      LINK_DEPENDENT_LIBRARIES may form a cycle if set incorrectly by hand
      (though CMake should never generate one).  In either case, do not follow
      the cycle forever when following the dependent shared library closure.
      We only need to add dependency edges to the constraint graph once.
      Add "LinkInterfaceLoop" test to cover this case.
    • Brad King's avatar
      Add infrastructure for CMake-only tests · 9a20abf0
      Brad King authored
      Some tests only need to run CMake to configure and generate a build
      tree, but not actually perform the build.  Add a new "Tests/CMakeOnly"
      directory dedicated for this purpose.  Add a helper script to drive each
      test by creating a fresh build tree and running CMake on it.  Add macro
      "add_CMakeOnly_test" to help create tests using the script.
  17. 23 Dec, 2011 8 commits
  18. 20 Dec, 2011 1 commit
    • Bill Hoffman's avatar
      Fix the case where cmake --build failed with two project cmds in one file. · 5badf5f7
      Bill Hoffman authored
      This adds a test that uses two project commands in the same CMakeLists.txt
      file.  It also adds a fix so that cmake --build will work in that case.
      The fix sets the name of the last project command in the top level
      CMakeLists.txt in the cache variable CMAKE_PROJECT_NAME.  This variable
      is used by cmake --build to find the project name.