View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0012299 | CMake | CMake | public | 2011-06-22 15:34 | 2012-01-02 15:56 | ||||
Reporter | Steven Velez | ||||||||
Assigned To | David Cole | ||||||||
Priority | normal | Severity | feature | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | Microsoft Visual Studio 10 | OS | Microsoft Windows | OS Version | 7 | ||||
Product Version | CMake 2.8.4 | ||||||||
Target Version | CMake 2.8.6 | Fixed in Version | CMake 2.8.6 | ||||||
Summary | 0012299: Visual Studio 10 generation does not support SCC Integration | ||||||||
Description | The 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 Reproduce | add 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 Information | I 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. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | 0001-SCC-Support-for-VS10.patch [^] (1,781 bytes) 2011-06-22 15:35 [Show Content] | ||||||||
Relationships | |
Relationships |
Notes | |
(0027100) Grant Limberg (reporter) 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 (manager) 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 (manager) 2012-01-02 15:56 |
Closing resolved issues that have not been updated in more than 4 months. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2011-06-22 15:35 | Steven Velez | New Issue | |
2011-06-22 15:35 | Steven Velez | File Added: 0001-SCC-Support-for-VS10.patch | |
2011-07-28 17:00 | Grant Limberg | Note Added: 0027100 | |
2011-07-29 08:46 | David Cole | Assigned To | => David Cole |
2011-07-29 08:46 | David Cole | Status | new => assigned |
2011-07-29 11:35 | David Cole | Target Version | => CMake 2.8.6 |
2011-07-29 14:56 | David Cole | Note Added: 0027120 | |
2011-07-29 14:56 | David Cole | Status | assigned => resolved |
2011-07-29 14:56 | David Cole | Fixed in Version | => CMake 2.8.6 |
2011-07-29 14:56 | David Cole | Resolution | open => fixed |
2012-01-02 15:56 | David Cole | Note Added: 0028109 | |
2012-01-02 15:56 | David Cole | Status | resolved => closed |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |