ExternalData: Fix test on make tools not supporting spaces

Do not add the "DATA{Data Space.dat}" when the native build tool does
not support spaces.
Merge topic 'ExternalData-spaces' into next

c5731d1 ExternalData: Fix test on make tools not supporting spaces
Tests: Replace exec_program with execute_process

Drop use of the old exec_program command from CMake's own CMakeLists.txt
files.
Tests: Generalize decision for 'make' tool supporting spaces

Some make tools do not support spaces inside the source tree paths.
Decide early whether to add tests that depend on support for spaces so
we can use the result in a decision for any test.
ExternalData: Test content link with a space in its name

Extend the Module.ExternalData test to cover a DATA{} reference whose
name contains a space.  Skip the case when the native build tool does
not support spaces.
Merge topic 'ExternalData-spaces' into next

55f0148 ExternalData: Test content link with a space in its name
d45eb35 Tests: Generalize decision for 'make' tool supporting spaces
ef8b2fd Tests: Replace exec_program with execute_process
automoc: Add source file to target early to set the linker language

Previously, GetIncludeDirectories was called before calling
target->AddSourceFile(mocCppSource). Since commit a1c4905f (Use the
link information as a source of compile definitions and
includes., 2013-02-12), the include directories are determined by
the link information.

Valid link information requires that the linker language can be
determined, which depends on the source files languages and the
dependent targets languages. In the case of the no_link_languages
target in the unit test, there are no dependencies and the additional
source file no_link_languages_automoc.cpp is added to the target
at generate-time. That file can be used to determine the linker
language, but it must be added to the target before calling
GetIncludeDirectories.
Merge topic 'fix-automoc-linker-language' into next

79568f9 automoc: Add source file to target early to set the linker language
FPHSA: Add FOUND_VAR option to specify _FOUND variable name

In the new mode FPHSA now accepts a FOUND_VAR option, which can be set
either to ExactCase_FOUND or UPPERCASE_FOUND, no other values are
accepted.  Also add tests for that, including failure.

Alex
FPHSA: improve documentation

Alex
Merge topic 'FPHSA_FOUND_VAR_OPTION' into next

c1f5780 FPHSA: improve documentation
7bb1abe FPHSA: Add FOUND_VAR option to specify _FOUND variable name