On 02/01/2016 07:07 PM, Novosielski, Ryan wrote: >> On Feb 1, 2016, at 18:49, Ben Webb ben@salilab.org wrote: >> I'm not sure what you mean here... but we've built IMP with various >> versions of OpenCV, the oldest being 2.1 and the newest being 2.3. > During the build process, it reports that it doesn't find OpenCV > version 2.1 or 2.2. It wasn't clear to me for a while whether it was > finding 2.3 and discounting it because it was the wrong version number, > or whether I had a problem finding OpenCV at all.
Ah, I see what you mean. Yes, the cmake output can be a bit sparse - you have to look in an obscure location (I think CMakeFiles/CMakeError.log) to see more useful information - but ours is a bit sparse too. Should be addressed in b0f5340d.
>> RHEL and CentOS don't yet package OpenCV in any form (not even in EPEL) > I actually looked today, BTW -- that's not true anymore, apparently. > CentOS packages OpenCV 2.4.5.
Oh, you're right, and I misremembered the OpenCV situation here. RHEL *does* package OpenCV, but it's a really old version in EPEL5 and RHEL6. I hadn't noticed that they finally updated it in RHEL7. Our RPM should pull in the system copy of OpenCV on RHEL7 now, as of becfba59.
>> Boost 1.60 is broken - nothing we can do about that, sorry. Complain to >> the Boost folks. The relevant bug is here: >> https://svn.boost.org/trac/boost/ticket/11880 > That's OK. A note on the website would be good though
Sure, done in f0f06deb.
>> RHEL 7 ships Boost 1.53 though so isn't affected. If you really want to >> use your own copy of Boost, you'll need to patch it yourself. > That only applies if I am using 1.60.0, right?
Right - 1.60.0 is the only version I've noticed as being broken. And we've definitely built with 1.59.0.
Ben