MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013614CMakeCMakepublic2012-10-30 08:512016-06-10 14:31
ReporterHendrik Sattler 
Assigned ToKitware Robot 
PrioritynormalSeveritytweakReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake 2.8.9 
Target VersionFixed in Version 
Summary0013614: Allow setting VC_SCC_PROVIDER for ALL_BUILD target (e.g. in Visual Studio 10)
DescriptionHi,

My main CMakeLists.txt file does not contain any targets itself but uses add_subdirectory(). This results in that CMakeLists.txt file to be part of the ALL_BUILD project the the Visual Studio 10 Solution.

Sadly, I cannot set any properties for this target (VS project), so I cannot checkin/-out that file in Visual Studio.

One possible fix (and probably making the common use of SCC easier: there is usually only one for a whole project) is to allow setting these flags not only as target properties but also as global properties.

Regards...
Steps To Reproduce
Additional Information
Tagsresolved
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-10-30 08:51Hendrik SattlerNew Issue
2012-10-30 08:53Hendrik SattlerNote Added: 0031350
2014-08-25 05:54Hendrik SattlerNote Added: 0036672
2015-11-11 04:11Hendrik SattlerTag Attached: resolved
2016-06-10 14:28Kitware RobotNote Added: 0042137
2016-06-10 14:28Kitware RobotStatusnew => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0031350)
Hendrik Sattler   
2012-10-30 08:53   
VC_SCC_PROVIDER should read VS_SCC_PROVIDER
(0036672)
Hendrik Sattler   
2014-08-25 05:54   
This is solved in 2.8.11 with e.g.

set_property ( DIRECTORY . APPEND PROPERTY VS_GLOBAL_SECTION_PRE_RationalClearCase
  SourceControlProvider=RationalClearCase
)
(0042137)
Kitware Robot   
2016-06-10 14:28   
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.