hi michael,
thanks for the tip, this makes a lot of sense. unfortunately, the
following does not work:
add_custom_command(TARGET libopenrave POST_BUILD COMMAND
${CMAKE_COMMAND} -E create_symlink $TARGET_FILE_NAME:libopenrave0.3
$TARGET_FILE_NAME:libopenrave )
doing a grep on build.make, i see
hi michael,
thanks for the tip, this makes a lot of sense. unfortunately, the
following does not work:
add_custom_command(TARGET libopenrave POST_BUILD COMMAND
${CMAKE_COMMAND} -E create_symlink $TARGET_FILE_NAME:libopenrave0.3
$TARGET_FILE_NAME:libopenrave )
doing a grep on
On 05/04/2011 11:51 AM, Rolf Eike Beer wrote:
hi michael,
thanks for the tip, this makes a lot of sense. unfortunately, the
following does not work:
add_custom_command(TARGET libopenrave POST_BUILD COMMAND
${CMAKE_COMMAND} -E create_symlink $TARGET_FILE_NAME:libopenrave0.3
Hi all,
We would like to add a 'make altinstall' option similar to python's
altinstall so that it doesn't install symlinks that clobber the system
install's symlinks for our program.
Basically, a normal install does:
program0.3
program - program0.3(using install(CODE))
On 04/24/2011 08:35 AM, Rosen Diankov wrote:
Hi all,
We would like to add a 'make altinstall' option similar to python's
altinstall so that it doesn't install symlinks that clobber the system
install's symlinks for our program.
Basically, a normal install does:
program0.3
program -