On 9/3/14, 11:31 AM, Frank Thommen wrote:
I am building IMP by using a HDF5 installation in a non-standard location. When running cmake with the HDF5_* options, HDF5 is found when configuring some modules, but not found when configuring others.
Are you sure HDF5 really isn't found? (If that were the case, any module that requires it would be disabled.) cmake checks to see if a pkgconfig package is available first before it looks for headers, and will complain if it doesn't find one. So you'll see it complain that "foo package not found" followed by "foo.h found in /include/path". I find this confusing but that's presumably a decision the cmake folks made at some point - not under our control.
Ben -- ben@salilab.org http://salilab.org/~ben/ "It is a capital mistake to theorize before one has data." - Sir Arthur Conan Doyle