MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012429CMakeCMakepublic2011-08-29 11:332016-06-10 14:31
ReporterMathias Gaunard 
Assigned ToKitware Robot 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake 2.8.5 
Target VersionFixed in Version 
Summary0012429: Targets cannot be created in an arbitrary scope
DescriptionIn certain scenarios I would have found useful to have the ability put a custom command or target should appear into a parent scope.

Unfortunately there seems to be no way to do this, short of abusing the binary_dir argument to add_subdirectory and setting CMP0013 to OLD.

I've attached a project that demonstrates how to abuse add_subdirectory to do this. I would like to know how good this technique is and whether it can break in certain situations or with certain generators.

Otherwise, what would be the best way to support this feature?
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filesbz2 project.tar.bz2 (546) 2011-08-29 11:33
https://public.kitware.com/Bug/file/4031/project.tar.bz2
Issue History
Date ModifiedUsernameFieldChange
2011-08-29 11:33Mathias GaunardNew Issue
2011-08-29 11:33Mathias GaunardFile Added: project.tar.bz2
2012-08-11 11:38David ColeStatusnew => backlog
2012-08-11 11:38David ColeNote Added: 0030299
2016-06-10 14:28Kitware RobotNote Added: 0041897
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
(0030299)
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.
(0041897)
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.