|View Issue Details [ Jump to Notes ]||[ Print ]|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0013162||CMake||CMake||public||2012-04-24 01:22||2016-06-10 14:31|
|Assigned To||Kitware Robot|
|Platform||Mac||OS||OS X||OS Version||10.7|
|Product Version||CMake 2.8.7|
|Target Version||CMake 2.8.12||Fixed in Version|
|Summary||0013162: create_symlink command portability|
|Description||This command could be made to work on many-many Windows systems these days. Bonus: if symlinking not available, copy files instead.|
|Tags||No tags attached.|
Brad King (manager)
|Comment 0012986:0028671 is relevant here too. An implementation would need to detect if the symlink can be created without user/manual intervention and if not do something else. IMO silently copying instead of linking is not a general solution. It is only "right" in particular use cases.|
Eric NOULARD (developer)
Then may be we "just" need two -E commands:
create_symlink_or_copy old new
this one would create a symlink or make a copy as a fallback
this one should have the same fail cases as "copy".
create_symlink old new
this one would create a symlink if possible (without user intervention)
or fail if
- user intervention is needed
- symlink is not supported.
Probably that some built-in CMAKE_CAN_SYMLINK variable could be defined
in order to make it possible to programmatically check whether if symlink
is supported on the current platform.
May be a useful link:
David Cole (manager)
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.
David Cole (manager)
These bugs were deferred from target version 2.8.10 to 2.8.11 based on the responses to this email thread on the CMake developer's mailing list:
Kitware Robot (administrator)
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.
|2012-04-24 01:22||Dave Abrahams||New Issue|
|2012-04-24 08:45||Brad King||Relationship added||related to 0012376|
|2012-04-24 08:48||Brad King||Relationship added||has duplicate 0012986|
|2012-04-24 08:51||Brad King||Note Added: 0029320|
|2012-04-25 10:04||Eric NOULARD||Note Added: 0029341|
|2012-08-11 21:35||David Cole||Status||new => backlog|
|2012-08-11 21:35||David Cole||Note Added: 0030412|
|2012-08-14 11:22||David Cole||Status||backlog => new|
|2012-08-14 11:22||David Cole||Target Version||=> CMake 2.8.10|
|2012-10-18 11:16||David Cole||Target Version||CMake 2.8.10 => CMake 2.8.11|
|2012-10-18 11:17||David Cole||Note Added: 0031268|
|2013-05-17 09:33||Robert Maynard||Target Version||CMake 2.8.11 => CMake 2.8.12|
|2016-06-10 14:28||Kitware Robot||Note Added: 0042031|
|2016-06-10 14:28||Kitware Robot||Status||new => resolved|
|2016-06-10 14:28||Kitware Robot||Resolution||open => moved|
|2016-06-10 14:28||Kitware Robot||Assigned To||=> Kitware Robot|
|2016-06-10 14:31||Kitware Robot||Status||resolved => closed|
|Copyright © 2000 - 2018 MantisBT Team|