diff options
| author | Brad King <brad.king@kitware.com> | 2014-10-10 13:57:07 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2014-10-13 12:20:05 (GMT) |
| commit | f4c5eade787f4f0a6e33fe029c2816580db06041 (patch) | |
| tree | 549735d61c4a2e81c9a05a0e9613b0bc756c8ce4 /Tests/VSResource/test.rc | |
| parent | 5ab9aa62fe1e5e1e74bafc69bf0e8d16f118ac9d (diff) | |
| download | CMake-f4c5eade787f4f0a6e33fe029c2816580db06041.zip CMake-f4c5eade787f4f0a6e33fe029c2816580db06041.tar.gz CMake-f4c5eade787f4f0a6e33fe029c2816580db06041.tar.bz2 | |
Ninja: Fix RC include directories regression
Changes in commit b9aa5041 (cmLocalGenerator: Simplify GetIncludeFlags
output formatting, 2014-03-04) caused Windows Resource Compiler include
directories to be computed as relative paths in the Ninja generator.
This breaks the cmcldeps handling of include paths. The reason for the
regression is that several cmLocalGenerator::GetIncludeFlags callers
treated the fourth "bool forResponseFile" argument as if it controlled
whether include directories were a full path. It actually did control
that by accident until the above commit.
Add an explicit "bool forceFullPaths" argument to GetIncludeFlags
and thread the value through ConvertToIncludeReference as needed.
Update GetIncludeFlags call sites that really wanted to control the
forResponseFile setting to be aware of the new argument. Extend the
VSResource test to cover this case.
Diffstat (limited to 'Tests/VSResource/test.rc')
| -rw-r--r-- | Tests/VSResource/test.rc | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Tests/VSResource/test.rc b/Tests/VSResource/test.rc index 4ce4b53..0de4683 100644 --- a/Tests/VSResource/test.rc +++ b/Tests/VSResource/test.rc @@ -1,4 +1,7 @@ #ifdef CMAKE_RCDEFINE +# ifndef CMAKE_RC_NO_INCLUDE +# include <include.rc> +# endif // This line can compile with either an unquoted or a quoted string 1025 TEXTFILE CMAKE_RCDEFINE |