[CMake] SCC bindings missing AUXPATH support?

Robert Dailey rcdailey at gmail.com
Tue Nov 1 07:40:51 EDT 2011


On Mon, Oct 31, 2011 at 11:59 PM, Steven Velez <sbv1976 at gmail.com> wrote:

> Hi Robert,
>
> I reviewed the patch, and I am not sure vsAuxPath should be a
> requirement.  As I stated earlier, we've gotten the binding to work
> acceptably without it and I assume others have as well.  Further, some
> users may prefer to enter their connection information in to the
> perforce dialog on first invocation instead of having to configure the
> cmake cache to setup their bindings.
>

I never said it wouldn't work without AuxPath, I am just stating that it
works better with it. AuxPath is where the connection string is placed.

Each person that uses CMake is different and I see no reason why AuxPath
should not be an available option to the user, especially since I've
already done the work of adding it in.

If users want to continuously press "OK" on the perforce connection dialog
for every project opened in the solution, that's fine by me but I certainly
don't want to deal with that annoying behavior.


> To be clear, I have no objections to adding AuxPath support (not that
> my objections count for anything around here).  Its that just as it
> stands now, if you don't supply it, you won't get any bindings.
>

I can easily make it optional. I was just following the design already in
place, which forces all parameters to be required.


> Also, you may have better results getting your patch integrated by
> opening a defect in cmake's bug tracker and attaching the patch to
> that.  The preferred patch generation method is also described here:
> http://www.mail-archive.com/cmake@cmake.org/msg36619.html


Thanks for the info!!


> By the way, as I stated in an earlier mail, if you wish to pursue this
> further, if you change "C:/Code/work/sandbox" to "..\..\.." where that
> path points to "C:\Code\work\sandbox" relative to the target being
> bound, you should have better results.
>

I read your last email but I fail to see the logic behind why a relative
path works better than an absolute one. Based on my tests, using an
absolute path has not resulted in any prompts to save the solution/projects.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20111101/8927d647/attachment-0001.htm>


More information about the CMake mailing list