View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0010485CMakeCMakepublic2010-03-30 06:142011-01-12 07:25
ReporterChristoph Höger 
Assigned ToBrad King 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product VersionCMake-2-8 
Target VersionCMake 2.8.4Fixed in VersionCMake 2.8.4 
Summary0010485: add_custom_command searches literally for file name targets
DescriptionWhen using something like

set(mydir src/)
add_custom_command(OUTPUT ${mydir}/foo

and

add_library(bar ${mydir}/foo)

The file src/foo will not be generated (since the custom command is triggered literally by "src//foo").
Also there is no error reported by cmake about a missing source file src/foo or src//foo.
This means that partially cmake handles filenames by normalizing them somehow and partially not.
I'd suggest applying the normalizing routine to custom commands too.

TagsNo tags attached.
Attached Files

 Relationships
related to 0011973closedBrad King double-slashes in paths breaks dependency resolution 

  Notes
(0024139)
Brad King (manager)
2010-12-15 08:51

 Thanks, fixed:

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a75a0a14 [^]

 Issue History
Date Modified Username Field Change
2010-03-30 06:14 Christoph Höger New Issue
2010-12-14 18:22 David Cole Assigned To => Brad King
2010-12-14 18:22 David Cole Status new => assigned
2010-12-15 08:51 Brad King Note Added: 0024139
2010-12-15 08:51 Brad King Status assigned => closed
2010-12-15 08:51 Brad King Resolution open => fixed
2011-01-12 07:25 David Cole Fixed in Version => CMake 2.8.4
2011-01-12 07:25 David Cole Target Version => CMake 2.8.4
2011-03-29 18:09 Brad King Relationship added related to 0011973

Copyright © 2000 - 2018 MantisBT Team