MakefileGenerator: only remove flags that match as a whole

On the Mac this was incorrectly removing -w from -Wno-write-strings
CMake Nightly Date Stamp
CMake Nightly Date Stamp
CPack: don't write internal variables to CPackConfig.cmake

The internal variables CPACK_ADDCOMP_COMPONENTS,
CPACK_ADDCOMP_STR and CPACK_ADDCOMP_UNAME were being needlessly
exported to CPackConfig.cmake.
Prefixing them with an underscore prevents this.

CPACK_ADDCOMP_STR was particularily problematic since it contains
unescaped quotes.
Merge topic 'cpack-internal-variables' into next

7621ad6 CPack: don't write internal variables to CPackConfig.cmake
89f6857 CMake Nightly Date Stamp
c524bdc CMake Nightly Date Stamp
Merge topic 'fix-remove-forbidden-flags' into next

9c57bd5 MakefileGenerator: only remove flags that match as a whole
Fix boog.
Merge topic 'cross-compiling-toolchain-variables' into next

853a479 Fix boog.
Introduce CMAKE_STAGING_PREFIX variable.

This variable can be useful in cross-compiling contexts where the
sysroot is read-only or where the sysroot should otherwise remain
pristine.

If the new CMAKE_STAGING_PREFIX variable is set, it is used instead
of CMAKE_INSTALL_PREFIX when generating the installation rules in
cmake_install.cmake.

This way, the CMAKE_INSTALL_PREFIX variable
always refers to the installation prefix on the target device, regardless
of whether host==target.

If any -rpath paths passed to the linker contain the CMAKE_STAGING_PREFIX,
the matching path fragments are replaced with the CMAKE_INSTALL_PREFIX.
Matching paths in the -rpath-link are not transformed.

The cross-prefix usr-move workaround is assumed not to require extension
regarding CMAKE_STAGING_PREFIX. The staging area is a single prefix, so
there is no scope for cross-prefix symlinks. The CMAKE_INSTALL_PREFIX
is still used to determine the workaround path, and that variable
remains the relevant one even if CMAKE_STAGING_PREFIX is used. If the
generated export files are deployed to the target, the workaround
will still be in place, and still be employed if required.
Merge topic 'cross-compiling-toolchain-variables' into next

1fb9f02 Introduce CMAKE_STAGING_PREFIX variable.
Add test.
Merge topic 'cross-compiling-toolchain-variables' into next

a8fd336 Add test.
Introduce CMAKE_STAGING_PREFIX variable.

This variable can be useful in cross-compiling contexts where the
sysroot is read-only or where the sysroot should otherwise remain
pristine.

If the new CMAKE_STAGING_PREFIX variable is set, it is used instead
of CMAKE_INSTALL_PREFIX when generating the installation rules in
cmake_install.cmake.

This way, the CMAKE_INSTALL_PREFIX variable
always refers to the installation prefix on the target device, regardless
of whether host==target.

If any -rpath paths passed to the linker contain the CMAKE_STAGING_PREFIX,
the matching path fragments are replaced with the CMAKE_INSTALL_PREFIX.
Matching paths in the -rpath-link are not transformed.

The cross-prefix usr-move workaround is assumed not to require extension
regarding CMAKE_STAGING_PREFIX. The staging area is a single prefix, so
there is no scope for cross-prefix symlinks. The CMAKE_INSTALL_PREFIX
is still used to determine the workaround path, and that variable
remains the relevant one even if CMAKE_STAGING_PREFIX is used. If the
generated export files are deployed to the target, the workaround
will still be in place, and still be employed if required.
Merge topic 'cross-compiling-toolchain-variables' into next

620c529 Introduce CMAKE_STAGING_PREFIX variable.
Test installation to stage.
Remove unused.
Fix path quoting.
Merge topic 'cross-compiling-toolchain-variables' into next

264725c Fix path quoting.
a468f46 Remove unused.
7e0f3f2 Test installation to stage.
Add error diagnosis.
Merge topic 'cross-compiling-toolchain-variables' into next

572c56a Add error diagnosis.