MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012065CMakeCMakepublic2011-04-09 17:592015-03-02 08:57
ReporterClinton Stimpson 
Assigned ToClinton Stimpson 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0012065: file(RELATIVE_PATH ...) gives wrong results with extra "./"
Description
set(fil /path/to/one)

set(dir /path/to/.)
file(RELATIVE_PATH rel ${dir} ${fil})
message(STATUS "rel=${rel}")
# output is "rel=../one" -- wrong

set(dir /path/to/././././.)
# with get_filename_component it gives the "rel=one" instead of
# rel=../../../../../one
get_filename_component(dir /path/to/././././. ABSOLUTE)
file(RELATIVE_PATH rel ${dir} ${fil})
message(STATUS "rel=${rel}")
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0014462closed Clinton Stimpson RELATIVE_PATH does not return a relative path when there is a double slash in the original path 
has duplicate 0014765closed  file(RELATIVE_PATH) does not handle /../ and /./ properly 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-04-09 17:59Clinton StimpsonNew Issue
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030251
2014-02-19 15:57Brad KingRelationship addedhas duplicate 0014765
2014-02-19 15:58Brad KingRelationship addedrelated to 0014462
2014-09-09 10:31Clinton StimpsonAssigned To => Clinton Stimpson
2014-09-09 10:31Clinton StimpsonStatusbacklog => assigned
2014-09-09 10:33Clinton StimpsonNote Added: 0036756
2014-09-09 10:33Clinton StimpsonStatusassigned => resolved
2014-09-09 10:33Clinton StimpsonResolutionopen => fixed
2015-03-02 08:57Robert MaynardNote Added: 0038107
2015-03-02 08:57Robert MaynardStatusresolved => closed

Notes
(0030251)
David Cole   
2012-08-11 11:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0036756)
Clinton Stimpson   
2014-09-09 10:33   
http://www.cmake.org/gitweb?p=cmake.git;a=commit;h=92b582a [^]
(0038107)
Robert Maynard   
2015-03-02 08:57   
Closing resolved issues that have not been updated in more than 4 months.