VS: Fix CMAKE_<LANG>_COMPILER detection with Intel toolset (#14471)

When the platform toolset is from Intel, look for "icl.exe" instead of
"cl.exe".
CMake Nightly Date Stamp
CMP0024: Store the fact of included export in global generator.

Storing it in the makefile means that the policy does not trigger
when include and export are in differing directories.
Merge topic 'fix-CMP0024-multiple-directories' into next

af1f698 CMP0024: Store the fact of included export in global generator.
cmExportInstallFileGenerator: Fix comment to match reality.

It was copied from cmExportBuildFileGenerator.
OS X: Encode -F framework search flag in per-language platform variable

Compilers for languages other than C and C++ on OS X may not understand
the -F framework search flag.  Create a new platform information
variable CMAKE_<LANG>_FRAMEWORK_SEARCH_FLAG to hold the flag, and set it
for C and CXX lanugages in the Platform/Darwin module.

Reported-by: Vittorio Giovara <vittorio.giovara@gmail.com>
Merge topic 'osx-framework-search-flag' into next

2e13c36 OS X: Encode -F framework search flag in per-language platform variable
872db62 CMake Nightly Date Stamp
Exclude Borland makefiles from this test.
Merge topic 'INTERFACE_LIBRARY-build-targets' into next

7a74a4f Exclude Borland makefiles from this test.
Create make rules for INTERFACE_LIBRARY targets.

The result is that the depends of the target are created.

So,

 add_library(somelib foo.cpp)
 add_library(anotherlib EXCLUDE_FROM_ALL foo.cpp)
 add_library(extra EXCLUDE_FROM_ALL foo.cpp)
 target_link_libraries(anotherlib extra)

 add_library(iface INTERFACE)
 target_link_libraries(iface INTERFACE anotherlib)

Executing 'make iface' will result in the anotherlib and extra targets
being made.

Adding a regular executable to the INTERFACE of an INTERFACE_LIBRARY
will not result in the executable being built with 'make iface' because
of the logic in cmComputeTargetDepends::AddTargetDepend.

So far, this is implemented only for the Makefile generator. Other
generators will follow if this feature is possible for them.
Merge topic 'INTERFACE_LIBRARY-build-targets' into next

26344a7 Create make rules for INTERFACE_LIBRARY targets.
Merge topic 'vs-intel-compiler-exe' into next

d10a597 VS: Fix CMAKE_<LANG>_COMPILER detection with Intel toolset (#14471)
Port away from reading the LOCATION property from build-targets.
Merge topic 'target-LOCATION-policy' into next

bc93346 Port away from reading the LOCATION property from build-targets.
cmTarget: Deprecate the LOCATION target property with a policy.

The final location and name of a build-target is not determined
until generate-time. However, reading the LOCATION property from
a target is currently allowed at configure time. Apart from creating
possibly-erroneous results, this has an impact on the implementation
of cmake itself, and prevents some major cleanups from being made.

Disallow reading LOCATION from build-targets with a policy. Port some
existing uses of it in CMake itself to use the TARGET_FILE generator
expression.
Merge topic 'target-LOCATION-policy' into next

8627fd2 cmTarget: Deprecate the LOCATION target property with a policy.
Only use the file(GENERATE) command with new CMake versions.
Merge topic 'target-LOCATION-policy' into next

9282c8f Only use the file(GENERATE) command with new CMake versions.
Add if(POLICY)
Merge topic 'target-LOCATION-policy' into next

eedb98d Add if(POLICY)