[CMake] Source control bindings feature in CMake needs better documentation

[Robert Dailey]

While waiting on a response I did some experimentation:


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

This seems to work in VS 2003 but the annoying thing is that when I open
the solution, every single project (about 120 of them) each prompt me for
my username, workspace, and server URL to perforce server.

Is there no way to specify this connection/user/workspace information in
CMake so that when I open the solution it already knows this stuff?

---------
Robert Dailey


On Mon, Oct 31, 2011 at 12:24 PM, Robert Dailey <rcdailey at gmail.com> wrote:

> Hey guys,
>
> Our team is running Perforce here at work and I want to setup any Visual
> Studio projects generated to use source control bindings for Perforce.
>
> The documentation for VS_SCC_PROJECTNAME, VS_SCC_LOCALPATH,
> VS_SCC_PROVIDER is pretty bad and I really have no clue on how to use
> these. Could someone explain what each is and possibly provide some
> examples on how they are used for Perforce?
>
> Thanks!!
>
> ---------
> Robert Dailey
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20111031/3b7689eb/attachment.htm>