I have an executable that links with HDF5 (by the way, is there any
plan to create a FindHDF5.cmake file?).
The problem is that I have two flavors of libraries:
libhdf5_cpp.a libhdf5.a
libhdf5_cpp.dylib libhdf5.dylib
When I do
set( HDF5_LIBRARIES hdf5_cpp hdf5
On Thu, 2009-06-11 at 16:49 -0600, James C. Sutherland wrote:
I have an executable that links with HDF5 (by the way, is there any
plan to create a FindHDF5.cmake file?).
The problem is that I have two flavors of libraries:
libhdf5_cpp.a libhdf5.a
libhdf5_cpp.dylib
On Jun 11, 2009, at 4:49 PM, James C. Sutherland wrote:
I have an executable that links with HDF5 (by the way, is there any
plan to create a FindHDF5.cmake file?).
The problem is that I have two flavors of libraries:
libhdf5_cpp.a libhdf5.a
libhdf5_cpp.dylib
On Thu, Jun 11, 2009 at 5:05 PM, James C. Sutherland
james.sutherl...@utah.edu wrote:
On Jun 11, 2009, at 4:49 PM, James C. Sutherland wrote:
I have an executable that links with HDF5 (by the way, is there any plan
to create a FindHDF5.cmake file?).
The problem is that I have two flavors
If you are distributing your application on a Mac, then there are
myriads of methods to distribute the shared libraries with the
application.
James,
Can you point me in the right direction?
I haven't yet tried this on Linux, so I don't know what land mines
await me there...
Thanks,
James,
If you distribute on OS X then there are some CMake facilities to
help you create a stand alone .app bundle. Basically it will run
install_name_tool on the dylibs to make sure they reference
dependent libraries that are stored inside the .app bundle. Usually
this is a real pain to do by
http://www.bluequartz.net/cgi-bin/gitweb/gitweb.cgi?p=MXADataModel.git;a=blob;f=Resources/CMake/MXAFindHDF5.cmake;h=f96bf33a9d0efd42488752e6eec0124532e367ef;hb=6b6079cc30c62ac5a672c5a7a50c359af064fbe5
is a FindHDF5.cmake file that I also borrowed from the paraview
project, then added features
If you distribute on OS X then there are some CMake facilities to
help you create a stand alone .app bundle. Basically it will run
install_name_tool on the dylibs to make sure they reference
dependent libraries that are stored inside the .app bundle. Usually
this is a real pain to do by hand
On Thu, Jun 11, 2009 at 8:46 PM, James C.
Sutherlandjames.sutherl...@utah.edu wrote:
If you distribute on OS X then there are some CMake facilities to
help you create a stand alone .app bundle. Basically it will run
install_name_tool on the dylibs to make sure they reference
dependent
