On 11/17/2011 5:26 PM, Clinton Stimpson wrote:
To get the desired behavior, we can automate
set(CMAKE_INSTALL_NAME_DIR @rpath)
I think it would be nice to have it be @rpath even in the build tree, but I
don't see that as a requirement. It could help avoid install name changes at
install
On Monday, November 21, 2011 01:41:57 pm James Bigler wrote:
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)
On Friday, November 18, 2011 04:59:36 am David Cole wrote:
On Thu, Nov 17, 2011 at 5:26 PM, Clinton Stimpson clin...@elemtech.com
wrote:
On Thursday, November 17, 2011 02:03:15 pm Brad King wrote:
On 11/17/2011 11:49 AM, Clinton Stimpson wrote:
I'm experimenting with using @rpath instead
I'm experimenting with using @rpath instead of @executable_path and
@loader_path, because @rpath is useful in some situations where the others
don't work as well. For example, I want to avoid setting DYLD_LIBRARY_PATH
when using a relocatable SDK. Using @rpath allows a user to embed a path
On 11/17/2011 11:49 AM, Clinton Stimpson wrote:
I'm experimenting with using @rpath instead of @executable_path and
@loader_path, because @rpath is useful in some situations where the others
don't work as well. For example, I want to avoid setting DYLD_LIBRARY_PATH
when using a relocatable
