CMake Nightly Date Stamp
Merge topic 'OpenBSD-patches'

f80ccac OpenBSD: Add paths for Qt3/Qt4
Merge topic 'add-timestamp-subcommands'

12d87c0 CMake: Fix dashboard build errors and warnings
e28ce24 CMake: Fix dashboard test failure
354ecc1 CMake: Fix dashboard warnings
d842d90 CMake: Stylistic changes and documentation tweaks
711e2b3 CMake: Add TIMESTAMP subcommand to string and file commands
Merge topic 'ConfigHelperMinorCommentFix'

8039bd0 CONFIGURE_PACKAGE_CONFIG_FILE(): improve generated comments
Merge topic 'skip-variable-re-expansion'

711b63f Add policy CMP0019 to skip include/link variable re-expansion
Merge topic 'TheRealAutomocIncludeDirFix'

acc2240 Automoc: get include dirs without stripping implicit include dirs off
Merge topic 'xcode-framework-paths'

f0d9385 Makefile: Use modern link information for framework search paths
2bc22bd Xcode: Add frameworks search paths from link dependeny closure (#13397)
Merge topic 'fix-13657-more-gcov47-output'

61ace1d CTest: Coverage handler: expect certain output lines from gcov 4.7 (#13657)
Merge branch 'master' into next
Documentation: Clarify handling of implicit link directories

The wording introduced in the parent commit sounds like CMake reads the
LIBRARY_PATH environment variable, but it is the toolchain that reads
it.
Documentation: Clarify handling of implicit link directories

Extend documentation for CMAKE_<LANG>_IMPLICIT_LINK_DIRECTORIES to
explain how it is used by CMake and how it can be influenced by
environment variables.

Inspired-by: Alex Neundorf <neundorf@kde.org>
Merge topic 'DocumentLIBRARY_PATH' into next

f249999 Documentation: Clarify handling of implicit link directories
Merge topic 'doc-implicit-link-dirs' into next

017d90c Documentation: Clarify handling of implicit link directories
OS X: Link with all framework search paths, not just the last

Refactoring in commit 8d674e78 (Ninja: move -LIBPATH behind -link
option, 2012-09-26) accidentally added code that overwrites the
framework search path flags on each iteration instead of appending.
Change '=' to '+=' to fix it.  This affects Makefile and Ninja
generators.
OS X: Detect implicit link directories on modern toolchains

We detect the implicit link directories for the toolchain by adding a
flag to get verbose output from the compiler front-end while linking the
ABI detection binary.  Newer OS X toolchains based on Clang do not add
the implicit link directories with -L options to their internal
invocation of "ld".  Instead they use a linker that comes with the
toolchain and is already configured with the proper directories.

Add the "-Wl,-v" option to ask "ld" to print its implicit directories.
It displays them in a block such as:

 Library search paths:
	/...

Parse this block to extract the implicit link directories.

While at it, remove the checks introduced by commit efaf335b (Skip
implicit link information on Xcode, 2009-07-23) and commit 5195a664
(Skip implicit link info for multiple OS X archs, 2009-09-22).  Discard
the non-system link directories added by Xcode.  Discard all detected
implicit libraries in the multi-architecture case but keep the
directories.  The directories are still useful without the libraries
just to suppress addition of explicit -L options for them.
OS X: Detect implicit linker framework search paths

Previously we hard-coded a list of implicit framework directories but
did not account for CMAKE_OSX_SYSROOT or for changes to the list across
OS X versions.  Instead we should automatically detect the framework
directories for the active toolchain.

The parent commit added the "-Wl,-v" option to ask "ld" to print its
implicit directories.  It displays a block such as:

 Framework search paths:
	/...

Parse this block to extract the list of framework directories.

Detection may fail on toolchains that do not list their framework
directories, such as older OS X linkers.  Always treat the paths

 <sdk>/Library/Frameworks
 <sdk>/System/Library/Frameworks
 <sdk>/Network/Library/Frameworks # Older OS X only
 /System/Library/Frameworks

as implicit.  Note that /System/Library/Frameworks should always be
considered implicit so that frameworks CMake finds there will not
override the SDK copies.
Merge topic 'osx-implicit-link-dirs' into next

cc676c3 OS X: Detect implicit linker framework search paths
2dd67c7 OS X: Detect implicit link directories on modern toolchains
ba58d0c OS X: Link with all framework search paths, not just the last