MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0016043CMakeCMakepublic2016-03-31 15:122016-06-10 14:31
ReporterZachary Turner 
Assigned ToKitware Robot 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake 3.5.1 
Target VersionFixed in Version 
Summary0016043: Support natvis source file type in the MSVC Project Generator
DescriptionStarting with Visual Studio 14 2015, vcxproj files can contain references to natvis files which enable custom debug visualizers for project specific types.

You specify these in the vcxproj file by including them in a <natvis> tag. Currently the MSVC project generator has no support for these. Through some hackery, it is still possible to get these files to appear in the vcxproj file with a <None> tag, and testing shows that it will work as long as the file has a .natvis extension, but a) this is undocumented / unsupported reliance on an implementation detail, b) it doesn't work if your file does not have a .natvis extension, and c) there could be some issues with doing this which we are unaware of.

It would be nice if you could write some CMake code like this:

`set_source_files_properties(foo.natvis LANGUAGE natvis)`

and this would cause the vcxproj generator to use a <natvis> tag instead of a <none> or <clcompile> tag, and this seems to fit well within CMake's language / generation model anyway.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-03-31 15:12Zachary TurnerNew Issue
2016-06-10 14:29Kitware RobotNote Added: 0042973
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0042973)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.