[cmake-developers] [CMake 0014529]: Leading UNC slashes stripped if include path contains repeated slashes

Mantis Bug Tracker mantis at public.kitware.com
Thu Oct 31 10:38:00 EDT 2013


The following issue has been SUBMITTED. 
====================================================================== 
http://public.kitware.com/Bug/view.php?id=14529 
====================================================================== 
Reported By:                Petr Kmoch
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   14529
Category:                   CMake
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2013-10-31 15:38 CET
Last Modified:              2013-10-31 15:38 CET
====================================================================== 
Summary:                    Leading UNC slashes stripped if include path
contains repeated slashes
Description: 
When a UNC path includes repeated slashes, CMake replaces all repeated slashes
by single slashes, including the ones at the beginning. The net effect is the
path is no longer a UNC path in the generated buildsystem.

Steps to Reproduce: 
include_directories(//unc/path_which/contains/repeated//slashes)
add_executable(foo ...)

#

The include path will be listed as "\unc\path_which\contains\repeated\slashes"
in the generated foo.vc[x]proj.

Additional Information: 
I've seen this behaviour with VS8 and VS10 generators when setting a UNC path in
include_directories(). I haven't tested this in other path-handling scenarios.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2013-10-31 15:38 Petr Kmoch     New Issue                                    
======================================================================




More information about the cmake-developers mailing list