MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001103CMakeCMakepublic2004-08-19 08:252010-12-08 15:38
ReporterKris Dekeyser 
Assigned ToBrad King 
PrioritylowSeverityfeatureReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOSOS Version
Product Version 
Target VersionCMake 2.8.4Fixed in VersionCMake 2.8.4 
Summary0001103: propagation mechanism for include paths
DescriptionIf a project A depends on project B and B uses a 3rd party library X and adds include search paths for library X, it would be nice if B's author could indicate these paths to be inherited by the dependent project A, so that A's auther can remain completely unaware of the dependency B->X.
Maybe an option to the INCLUDE_DIRECTORIES command could flag such paths.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0000115closed Brad King Automatic propagation of include directories. 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2007-10-12 11:12Bill HoffmanStatusnew => assigned
2007-10-12 11:31Brad KingNote Added: 0009442
2010-08-28 01:48Kovarththanan RajaratnamNote Added: 0021992
2010-08-28 01:48Kovarththanan RajaratnamNote Edited: 0021992
2010-11-10 15:01David ColeTarget Version => CMake 2.8.4
2010-12-07 17:14David ColeRelationship addedrelated to 0000115
2010-12-08 15:38David ColeNote Added: 0023812
2010-12-08 15:38David ColeStatusassigned => closed
2010-12-08 15:38David ColeResolutionopen => duplicate
2010-12-08 15:38David ColeFixed in Version => CMake 2.8.4

Notes
(0009442)
Brad King   
2007-10-12 11:31   
There is a plan to create "imported" library targets that will propagate build options. Something like this will be possible when the feature is complete.
(0021992)
Kovarththanan Rajaratnam   
2010-08-28 01:48   
This seems to be a duplicate of bug 115.
(0023812)
David Cole   
2010-12-08 15:38   
Decided to be a duplicate of 115 in the CMake 2.8.4 bug triage meeting, Dec. 8, 2010.