MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015588CMakeCMakepublic2015-05-27 09:192016-06-10 14:31
ReporterValerii Kanunik 
Assigned ToKitware Robot 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0015588: New behavior of ExternalProject_Add command
DescriptionExternalProject_Add provides great functionality but IMO very uncomfortable. The problem is that command perform all actions on build step and clean command removes all results.

Is it possible change command behavior (or provide new one for instance add_subproject) which:
1) Preforms download and configure steps along with configure step of main project
2) Does not add to clean target all unziped or downloaded files, but adds additional command (for inctance make clean-all or dist-clean) which does that.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0015611closed Kitware Robot ExternalProject_Add and find_package commands 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-05-27 09:19Valerii KanunikNew Issue
2015-06-12 04:39Valerii KanunikNote Added: 0038915
2015-06-15 08:40Brad KingRelationship addedrelated to 0015611
2016-06-10 14:29Kitware RobotNote Added: 0042784
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0038915)
Valerii Kanunik   
2015-06-12 04:39   
A little explanation of what the functionality required.

Usually to the project as an external projects adds libraries which do not change, for instance unit test frameworks etc. So it is required build them ones on configure step and forget about them. And then do make all and make clean for your work projects that will change.
(0042784)
Kitware Robot   
2016-06-10 14:29   
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.