CMake/Tests/VSResource/test.rc

#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

#ifndef CMAKE_RCDEFINE_NO_QUOTED_STRINGS
// This block can only be compiled if CMAKE_RCDEFINE preprocesses
// to a double quoted string
STRINGTABLE
BEGIN
  1026 CMAKE_RCDEFINE
END
#endif

#else
#error "resource compiler did not get defines from command line!"
#endif
Add flags to resource builds on vs 2010 with a test. 2010-12-21 09:17:21 -05:00			`#ifdef CMAKE_RCDEFINE`
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. 2014-10-10 09:57:07 -04:00			`# ifndef CMAKE_RC_NO_INCLUDE`
			`# include <include.rc>`
			`# endif`
VS10: Escape double quote chars in defines for rc files (#11695) To get rc defines to work in the VS10 IDE requires \" when constructing PreprocessorDefinitions strings. This is different than defines for cl. Also, per-file rc defines were not being generated. Fix that, too. 2011-01-25 18:54:36 -05:00
VSResource: Avoid windres /D with quoted spaces (#11695) Improve test: print out what's happening along the way. 2011-01-27 15:45:25 -05:00			`// This line can compile with either an unquoted or a quoted string`
			`1025 TEXTFILE CMAKE_RCDEFINE`

			`#ifndef CMAKE_RCDEFINE_NO_QUOTED_STRINGS`
			`// This block can only be compiled if CMAKE_RCDEFINE preprocesses`
			`// to a double quoted string`
VS10: Escape double quote chars in defines for rc files (#11695) To get rc defines to work in the VS10 IDE requires \" when constructing PreprocessorDefinitions strings. This is different than defines for cl. Also, per-file rc defines were not being generated. Fix that, too. 2011-01-25 18:54:36 -05:00			`STRINGTABLE`
			`BEGIN`
VSResource: Avoid windres /D with quoted spaces (#11695) Improve test: print out what's happening along the way. 2011-01-27 15:45:25 -05:00			`1026 CMAKE_RCDEFINE`
VS10: Escape double quote chars in defines for rc files (#11695) To get rc defines to work in the VS10 IDE requires \" when constructing PreprocessorDefinitions strings. This is different than defines for cl. Also, per-file rc defines were not being generated. Fix that, too. 2011-01-25 18:54:36 -05:00			`END`
VSResource: Avoid windres /D with quoted spaces (#11695) Improve test: print out what's happening along the way. 2011-01-27 15:45:25 -05:00			`#endif`

Add flags to resource builds on vs 2010 with a test. 2010-12-21 09:17:21 -05:00			`#else`
			`#error "resource compiler did not get defines from command line!"`
VS10: Escape double quote chars in defines for rc files (#11695) To get rc defines to work in the VS10 IDE requires \" when constructing PreprocessorDefinitions strings. This is different than defines for cl. Also, per-file rc defines were not being generated. Fix that, too. 2011-01-25 18:54:36 -05:00			`#endif`