MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012299CMakeCMakepublic2011-06-22 15:342012-01-02 15:56
ReporterSteven Velez 
Assigned ToDavid Cole 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionfixed 
PlatformMicrosoft Visual Studio 10OSMicrosoft WindowsOS Version7
Product VersionCMake 2.8.4 
Target VersionCMake 2.8.6Fixed in VersionCMake 2.8.6 
Summary0012299: Visual Studio 10 generation does not support SCC Integration
DescriptionThe CMake Documentation describes the following visual studio-specific project properties: VS_SCC_PROJECTNAME, VS_SCC_LOCALPATH, VS_SCC_PROVIDER which are intended to bind a source control provider to generated visual studio projects, but do not for Visual Studio 10 projects.
Steps To Reproduceadd a statement similar to the following to a cmake list file:

    set_target_properties( ${PROJECT_NAME} PROPERTIES
        VS_SCC_PROJECTNAME "Perforce Project"
        VS_SCC_LOCALPATH "${_PERFORCE_LOCAL_PATH}"
        VS_SCC_PROVIDER "MSSCCI:Perforce SCM" )

And generate a vs 10 project. You'll note that the behavior of the project is no different than if the properties had been omitted. vs 9 (and possibly earlier?) projects generated similarly behave correctly.
Additional InformationI have only tested this with the perforce SCC integration, but I am assuming that if the user enters the right values for the properties for their SCC provider, the change should work with it.
TagsNo tags attached.
Relationships
Attached Filespatch 0001-SCC-Support-for-VS10.patch (1,781) 2011-06-22 15:35
https://public.kitware.com/Bug/file/3957/0001-SCC-Support-for-VS10.patch
Issue History
Date ModifiedUsernameFieldChange
2011-06-22 15:35Steven VelezNew Issue
2011-06-22 15:35Steven VelezFile Added: 0001-SCC-Support-for-VS10.patch
2011-07-28 17:00Grant LimbergNote Added: 0027100
2011-07-29 08:46David ColeAssigned To => David Cole
2011-07-29 08:46David ColeStatusnew => assigned
2011-07-29 11:35David ColeTarget Version => CMake 2.8.6
2011-07-29 14:56David ColeNote Added: 0027120
2011-07-29 14:56David ColeStatusassigned => resolved
2011-07-29 14:56David ColeFixed in Version => CMake 2.8.6
2011-07-29 14:56David ColeResolutionopen => fixed
2012-01-02 15:56David ColeNote Added: 0028109
2012-01-02 15:56David ColeStatusresolved => closed

Notes
(0027100)
Grant Limberg   
2011-07-28 17:00   
This is still an issue with CMake 2.8.5.

I've tested this patch against the 2.8.5 tag of the main cmake git repository. I can confirm that P4SCC works again with this patch applied.
(0027120)
David Cole   
2011-07-29 14:56   
Fix pushed to CMake 'next' with this commit:

  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=05ddfbfe95c4536521084975be6e9cadf0ee05f9 [^]
(0028109)
David Cole   
2012-01-02 15:56   
Closing resolved issues that have not been updated in more than 4 months.