Would what you are proposing make the following easier?  This is how I
setup @rpath on my system.

Why do you need something special?  I use @rpath for the install name by
doing the following:

  if(RELEASE_PUBLIC)
    set_target_properties( my_target PROPERTIES
      INSTALL_NAME_DIR "@rpath"
      BUILD_WITH_INSTALL_RPATH ON
      )
  endif()

Then I do the following for my executables:

    if( RELEASE_INSTALL_BINARY_SAMPLES )
      target_link_libraries( ${target_name}
        -Wl,-rpath,@executable_path/.
        -Wl,-rpath,@executable_path/../../lib
        )
    elseif( RELEASE_PUBLIC)
      target_link_libraries( ${target_name}
        -Wl,-rpath,@executable_path/../lib
        )
    endif()

I also have some code to do some special stuff for BundleUtilities, but I'm
not sure if it's related to the rpath stuff.

James
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers

Reply via email to