1. 14 Jun, 2012 2 commits
  2. 13 Jun, 2012 1 commit
  3. 12 Jun, 2012 18 commits
  4. 11 Jun, 2012 2 commits
  5. 10 Jun, 2012 1 commit
  6. 09 Jun, 2012 1 commit
  7. 08 Jun, 2012 2 commits
  8. 07 Jun, 2012 5 commits
  9. 06 Jun, 2012 4 commits
    • Zaheer Chothia's avatar
      VS: Set Intel Fortran 13 project version · 8945489c
      Zaheer Chothia authored
      I have tested that it works with:
      
       Microsoft Visual Studio 10.0.40219.1
       Intel Visual Fortran 13.0.0.041 Beta Build 20120425
      8945489c
    • Brad King's avatar
      Makefile: Support directory names containing '=' (#12934) · ee6c1b8a
      Brad King authored
      Since commit c8ef6430 (Allow directory names containing '=' and warn if
      necessary, 2012-02-06) we allow directories with '=' instead of
      rejecting them as was previously done since commit 8704525f (Reject
      directory names containing '=', 2011-01-14).  However, we did not warn
      in all cases that '=' may cause failure, such as when it appears on the
      right-hand side of a dependency line.
      
      Both commits above were made assuming that '=' cannot be escaped in Make
      syntax, but it can be achieved with a variable:
      
        EQUALS = =
        left$(EQUALS)side : right$(EQUALS)side
      
      Use this approach to escape '=' in dependency lines, thus supporting
      the character in paths.
      
      All our tests now pass when CMake is built in source and build trees
      both containing '=', except for the "OutOfSource" test.  It fails in
      its coverage of the obscure "OutOfBinary" test case where part of the
      build tree is located outside the main build tree of the test.  The
      reason is that CMake must invoke a command like
      
        $(MAKE) -f /path/with=sign/build.make /path/with=sign/somefile
      
      but the make tool interprets the last argument as a variable assignment.
      This is an acceptable limitation, since the case is so obscure, in
      exchange for supporting '=' cleanly otherwise.
      ee6c1b8a
    • Brad King's avatar
      cmArchiveWrite: Clear fflags from archive entries · a34015d3
      Brad King authored
      When reading archive entries from disk strip any "fflags" entry headers
      that may have been loaded from the filesystem when libarchive is built
      with HAVE_STRUCT_STAT_ST_FLAGS (struct stat has 'st_flags').  The local
      filesystem flags are not useful for distribution.  Furthermore, GNU tar
      does not understand the "SCHILY.fflags" extended header used to store
      the flags in the archive.  Use the approach from commit e8558efa
      (cmArchiveWrite: Clear xattr and acl from entries, 2011-04-07) to remove
      the flags and avoid producing the non-portable extended header.
      a34015d3
    • Kitware Robot's avatar
      CMake Nightly Date Stamp · eb53bc27
      Kitware Robot authored
      eb53bc27
  10. 05 Jun, 2012 4 commits