1. 08 Oct, 2013 6 commits
  2. 19 Sep, 2013 1 commit
  3. 18 Sep, 2013 1 commit
  4. 17 Sep, 2013 2 commits
  5. 16 Sep, 2013 3 commits
  6. 15 Sep, 2013 1 commit
  7. 14 Sep, 2013 1 commit
  8. 13 Sep, 2013 6 commits
  9. 12 Sep, 2013 4 commits
  10. 11 Sep, 2013 3 commits
  11. 10 Sep, 2013 2 commits
  12. 09 Sep, 2013 3 commits
    • Brad King's avatar
      Merge topic 'no_track_configured_files' · 1e11708a
      Brad King authored and Kitware Robot's avatar Kitware Robot committed
      38571f2c cmMakefile: Do not track CMake temporary files.
      1e11708a
    • Robert Maynard's avatar
      cmMakefile: Do not track CMake temporary files. · 38571f2c
      Robert Maynard authored and Brad King's avatar Brad King committed
      Since commit ad502502 (cmMakefile: Track configured files so we can
      regenerate them, 2013-06-18) cmMakefile::ConfigureFile records the
      configured file as an output file generated by CMake.  The intention is
      that for make and ninja we can re-run CMake when one of the files it
      generates goes missing.  However, files configured temporarily in
      CMakeTmp directories by Check* modules do not live past the CMake
      invocation.
      
      We have to also track input files to the configure command.  In theory
      the input to a configure command could it self be a file that is going
      to be deleted later (output from a custom command or configure_file).
      38571f2c
    • Kitware Robot's avatar
      CMake Nightly Date Stamp · 92cc6539
      Kitware Robot authored
      92cc6539
  13. 08 Sep, 2013 1 commit
  14. 07 Sep, 2013 1 commit
  15. 06 Sep, 2013 1 commit
  16. 05 Sep, 2013 1 commit
  17. 04 Sep, 2013 1 commit
  18. 03 Sep, 2013 1 commit
  19. 02 Sep, 2013 1 commit