[cmake-developers] [CMake 0013666]: CMake fails to support existing custom VS_GLOBAL_* properties in VS10 (ProjectExtensions -> VisualStudio -> UserProperties)

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
====================================================================== 
http://public.kitware.com/Bug/view.php?id=13666 
====================================================================== 
Reported By:                Andreas Mohr
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   13666
Category:                   CMake
Reproducibility:            N/A
Severity:                   major
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2012-11-09 01:48 EST
Last Modified:              2012-11-09 01:48 EST
====================================================================== 
Summary:                    CMake fails to support existing custom VS_GLOBAL_*
properties in VS10 (ProjectExtensions -> VisualStudio -> UserProperties)
Description: 
While working on related functionality in vcproj2cmake, I noticed that while
CMake has VS_GLOBAL_* properties (which on VSx side are different things:
official *or* custom!) which are properly being generated into VS7 Globals
section,
in the VS10 generator there seems to be nothing done about it despite it seeming
to be expected to go into the ProjectExtensions element (VisualStudio ->
UserProperties sub elements).

A popular example of it would be the RESOURCE_FILE setting (or perhaps also
QtVersion?).

>From some Q&D analysis it appears that the properties that CMake manages
(improperly lumps together!!) as VS_GLOBAL_* are managed by VS in this way:
VS7/8: project-global attribute keys are the "official"/"fixed" VS_GLOBAL_*
values, whereas keys in Globals element are any user-custom values
VS10: element keys in Globals element are the "official"/"fixed" VS_GLOBAL_*
values, whereas keys in UserProperties (i.e. ProjectExtensions) element are any
user-custom values

Severity major since failing to generate the UserProperties section from all
non-official user-custom VS_GLOBAL_* properties kills all user-supplied project
properties on VS10, thus possibly causing major grief on user side, and it would
be rather very easy to correct.

Unless UserProperties section content happened to in fact be something different
on VS10 and these properties are not supposed to be generated there... (would
probably need some more analysis of known content in public sample project
files)

Thanks for listening! :)
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2012-11-09 01:48 Andreas Mohr   New Issue                                    
======================================================================