so let's say this: 1) If you want to use the opencv facilities, you need OpenCV >= 2.0 2) Because people may want more than one OpenCV version installed at a time, we will first make an attempt to find the variable OPENCV2 in LD_LIBRARY_PATH. - If the variable exists, but the dll loads fail, we abort the library import with a message to stdout. - if the variable does not exist, we assume that OpenCV 2.0 is the only version installed on the system and continue with the loading mechanism in place. If the user did not heed our instructions and instead is using OpenCV < 2.0, and something crashes. Shame on them. - if no library is found, fail gracefully as usual. How does that sound? Cheers! Chris 2009/11/4 Stéfan van der Walt <stefan@sun.ac.za>:
2009/11/4 Ralf Gommers <ralf.gommers@googlemail.com>:
3) a user wants to use scikits and has opencv 1.x but CANT get rid of it because they are using it for other things. - THIS user is a power user and shouldnt mind setting a variable in a file to point to their 2.0 libs.
Easy to do, and would only affect a few users. If this file is under version control that may be very annoying for developing though. If you set the variable you can never fast-forward anymore.
The user already has a variable like this in LD_LIBRARY_PATH, so I don't think we need to do anything other than document the way we find the library.
Stéfan