On Wed, Nov 4, 2009 at 5:39 PM, Chris Colbert <sccolbert@gmail.com> wrote:
There are so many different ways that people can configure their system. I think it fair for us to say, "if you want to do X you must have Y, otherwise you have to do Z"
Sure.
On Wed, Nov 4, 2009 at 5:38 PM, Chris Colbert <sccolbert@gmail.com> wrote:
I would rather make a global module variable in the OpenCV files that a user can set to the path of their OpenCV 2.0 libs if they have more than one version installed.
I see three situations: 1) a user wants to use scikits and doesnt have opencv - so they follow the build instructions and build 2.0 - no problems
I assume you mean "if he needs this opencv functionality". Please keep it optional.
2) a user wants to use scikits and has opencv 1.x - so they remove 1.x and build 2.0 - no problems 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. Cheers, Ralf