MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0005847CMakeCMakepublic2007-10-09 15:482016-06-10 14:30
Reporterufnoise 
Assigned ToBrad King 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0005847: please create "cmake -E install" command
DescriptionSuch a command is like copy, but will create the destination directory if it doesn't exist. This is similar to the unix install command.

A shell like equivalent would be
mkdir -p $DESTINATION
copy -f $DESTINATION/FILE $DESTINATION

Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2007-10-09 15:48ufnoiseNew Issue
2007-10-12 09:38Bill HoffmanStatusnew => assigned
2007-10-12 09:38Bill HoffmanAssigned To => Brad King
2007-10-12 09:58Brad KingNote Added: 0009427
2007-10-12 11:51ufnoiseNote Added: 0009447
2012-08-13 10:36Brad KingStatusassigned => backlog
2012-08-13 10:36Brad KingNote Added: 0030501
2016-06-10 14:27Kitware RobotNote Added: 0041391
2016-06-10 14:27Kitware RobotStatusbacklog => resolved
2016-06-10 14:27Kitware RobotResolutionopen => moved
2016-06-10 14:30Kitware RobotStatusresolved => closed

Notes
(0009427)
Brad King   
2007-10-12 09:58   
CMake provides very powerful installation rules through the CMake language. What is your use case for this?
(0009447)
ufnoise   
2007-10-12 11:51   
The case is:

The full path will be created during the copy. The necessary directories will be created if they don't exist. Using make_directory and copy together can be simplified into one install command.

The proper permissions can be set during the install. This can be used to make helper scripts executable.

The installation rules can only be run if you do a make install. Copy, and my proposed command, can be run as part of a regular build.
(0030501)
Brad King   
2012-08-13 10:36   
Sending issues I'm not actively working on to the backlog to await someone with time for them.

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 or contributor who has the bandwidth to take it on.
(0041391)
Kitware Robot   
2016-06-10 14:27   
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.