hi Pete
I use this script to clean my pluings in mac:
"./fix_lib $(Paraview_build_dir)/bin
'$(ParaviewPXDMFReader_lib_install_dir)/libPXDMFReader.dylib'"
- fix_lib ---
#!/bin/bash
stripString=$1
libpath=$2
insertString=@executable_path/../Libraries/
echo "Striping :" $stripStri
Hi David,
Thanks for the hints. My goal is to create a plugin that my collaborators
can load using the Kitware release of the ParaView binaries. I don't care
if my plugin is installed in the SuperBuild's ParaView.app.
In any case, I tried adding this to my plugin's CMakeLists.txt file:
SET(PAR
fixup_bundle is a cmake 2.8 feature that internally just runs
install_name_tool on Mac like you are considering doing manually.
I believe it is only tied the install target but I might be wrong on
that, ask on the cmake list.
See the ParaViewPlugins.cmake and Superbuild/CMakeLists.txt for how
our
Hello,
I have built ParaView-3.12.0 from the SuperBuild. Using otool, I noticed
that libraries had a hard-coded path to each shared library in the build
directory (otool -L ParaView-build/bin/libvtkPVServerManager.dylib).
However, after `make install`, I noticed each library was prefixed with
@e
