MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012365CMakeCMakepublic2011-07-27 17:072016-06-10 14:31
ReporterAndrew Fischer 
Assigned ToKitware Robot 
PrioritylowSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformLinuxOSArchlinuxOS VersionKernel 2.6.39
Product VersionCMake 2.8.5 
Target VersionFixed in Version 
Summary0012365: get_filename_component() can return incorrect ABSOLUTE and REALPATH values in a toolchain file
DescriptionIf you attempt to use get_filename_component() to return the ABSOLUTE or REALPATH path of the toolchain file name ${CMAKE_TOOLCHAIN_FILE}, while in that same toolchain file, the resulting path will be missing the project source directory the first time the toolchain file is called.

Example:

If the toolchain file is located at: /home/mydir/testproject/toolchain.cmake

The first time the toolchain file is called, both ABSOLUTE and REALPATH will return: /home/mydir/toolchain.cmake
Steps To Reproduce1. Create a minimal CMakeLists.txt file in some project directory (testproject/)

2. Create a sample toolchain file that uses get_filename_component to obtain the absolute or realpath to the ${CMAKE_TOOLCHAIN_FILE}. The attached file is a toolchain that demonstrates this.

3. Create a build directory (testproject/build)

4. From testproject/build, call the CMakeLists.txt with the attached toolchain file:

   cmake -DCMAKE_TOOLCHAIN_FILE=../toolchain.cmake ..

5. Observe how the initially printed out ABSOLUTE and REALPATH values are missing the testproject/ directory. Note the relative PATH entry will be correct.

Additional Information

TagsNo tags attached.
Relationships
Attached Files? toolchain.cmake (392) 2011-07-27 17:07
https://public.kitware.com/Bug/file/3983/toolchain.cmake
Issue History
Date ModifiedUsernameFieldChange
2011-07-27 17:07Andrew FischerNew Issue
2011-07-27 17:07Andrew FischerFile Added: toolchain.cmake
2012-08-11 11:38David ColeStatusnew => backlog
2012-08-11 11:38David ColeNote Added: 0030285
2016-06-10 14:28Kitware RobotNote Added: 0041873
2016-06-10 14:28Kitware RobotStatusbacklog => 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
(0030285)
David Cole   
2012-08-11 11:38   
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.
(0041873)
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.