CMake Nightly Date Stamp
Make the version check language specific.
Merge topic 'position-independent-targets' into next

73d825a Make the version check language specific.
Create output for the PIC and PIE options.
Merge topic 'position-independent-targets' into next

cb96f18 Create output for the PIC and PIE options.
Ninja: find mingw's resource compiler
Merge topic 'ninja-rspfile' into next

e3a1f72 Ninja: find mingw's resource compiler
cmArchiveWrite: Clear fflags from archive entries

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.
Merge topic 'archive-exclude-file-flags' into next

a34015d cmArchiveWrite: Clear fflags from archive entries
Makefile: Support directory names containing '=' (#12934)

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.
Merge topic 'makefile-escape-equals' into next

ee6c1b8 Makefile: Support directory names containing '=' (#12934)
VS: Set Intel Fortran 13 project version

I have tested that it works with:

 Microsoft Visual Studio 10.0.40219.1
 Intel Visual Fortran 13.0.0.041 Beta Build 20120425
Merge topic 'VS-Fortran-Intel-2013' into next

8945489 VS: Set Intel Fortran 13 project version
Avoid direct use of std::(o|)stringstream (#13272)

Older C++ compilers do not provide a standard std::stringstream.
Use our compatibility interfaces instead.
Merge branch 'no-std-stringstream' into ninja-rspfile

Conflicts:
	Source/cmGlobalNinjaGenerator.cxx
	Source/cmLocalNinjaGenerator.cxx
	Source/cmNinjaNormalTargetGenerator.cxx
Merge topic 'ninja-rspfile' into next

14cbd47 Merge branch 'no-std-stringstream' into ninja-rspfile
a6a3364 Avoid direct use of std::(o|)stringstream (#13272)
eb53bc2 CMake Nightly Date Stamp
Merge branch 'ninja-rspfile' into no-std-stringstream

Conflicts:
	Source/cmGlobalNinjaGenerator.cxx
	Source/cmLocalNinjaGenerator.cxx
	Source/cmNinjaNormalTargetGenerator.cxx
Merge topic 'no-std-stringstream' into next

89be611 Merge branch 'ninja-rspfile' into no-std-stringstream
Ninja: Avoid direct use of std::ostringstream (#13272)

Older C++ compilers do not provide a standard std::ostringstream.
Use cmOStringStream instead.
Merge topic 'no-std-stringstream' into next

5920592 Ninja: Avoid direct use of std::ostringstream (#13272)