On Feb 8, 2006, at 7:39 PM, Brad King wrote:
Mike Jackson wrote:
So if I turn on RPATH, and rpath uses -install_name, where do I
actually specify the RPATH to use? or can I specify the path at all?
Enabling VTK_USE_RPATH is intended for developers to be able to run
VTK programs from the
On Feb 8, 2006, at 10:37 AM, Brad King wrote:
Brad King wrote:
The VTK CMake code provides an interface to allow some
customization of the build. Create a file Common/
LocalUserOptions.cmake in either the VTK build tree or the source
tree. Add this line:
SET_TARGET_PROPERTIES(vtkCommon
The -install_name option is _already_ being specified by cmake
somewhere so when I tried your suggestion, I get an error during link
phase that the -install_name option is being specified twice.
Is there a master config file somewhere for cmake that I can just
edit? How else would cmake
Mike Jackson wrote:
The -install_name option is _already_ being specified by cmake
somewhere so when I tried your suggestion, I get an error during link
phase that the -install_name option is being specified twice.
Is there a master config file somewhere for cmake that I can just edit?
On Feb 8, 2006, at 7:00 PM, Brad King wrote:
Mike Jackson wrote:
The -install_name option is _already_ being specified by cmake
somewhere so when I tried your suggestion, I get an error during
link phase that the -install_name option is being specified twice.
Is there a master config
Mike Jackson wrote:
The -install_name option is _already_ being specified by cmake
somewhere so when I tried your suggestion, I get an error during
link phase that the -install_name option is being specified twice.
Is there a master config file somewhere for cmake that I can just
edit?
On Feb 8, 2006, at 9:06 PM, William A. Hoffman wrote:
At 07:28 PM 2/8/2006, Mike Jackson wrote:
So if I turn on RPATH, and rpath uses -install_name, where do I
actually specify the RPATH to use? or can I specify the path at all?
CMake will use the path to where the libraries are actually
I am building the official VTK 5.x release on OS X and I would like to
add a custom link argument for all the generated libraries. I am
building dynamic libraries and I would like to set the install-name
of each library to @executable_path/../Plugins so I can include the
libs in my .app package.
