Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Firstly, you don't have to accept my answer but I hope you read my comments and I think my problem was even bigger than yours; THE ENTIRE WINDOWS 7 64-bit machine was broken!!!!

Try this (It will also work for 2.2, 2.3, 2.4.2 and 2.4.3 (SVN trunk)!! http://www.aishack.in/2010/03/installing-and-configuring-opencv-2-0-on-windows/ BUT...make sure that you add the build/bin/debug and build/bin/release folders to the Additional Library Directories (in Linker > GENERAL and VC++ Directories in your DEBUG and RELEASE Configuration Property Sheet). Make sure that you copy and paste the .dll files FROM the build/bin/debug folder INTO YOUR SOLUTION'S (NOT PROJECT'S) DEBUG AND RELEASE folders. Do the same for the build/bin/release folder, BUT COPY THE .DLLs ONLY TO YOUR SOLUTIONS'S RELEASE FOLDER, NOT DEBUG.

One good thing is that having the DEBUG AND RELEASE DLLs in both DEBUG and RELEASE folders of your solutions ACTUALLY DOESN'T BREAK your code!! Those dlls are pretty much same in DEBUG and RELEASE configuration, may be few different macros and stuff!! At least, it didn't cause any trouble in my own code!!

Try this and see if it works :)!

Firstly, you don't have to accept my answer but I hope you read my comments and I think my problem was even bigger than yours; THE ENTIRE WINDOWS 7 64-bit machine was broken!!!!broken!!!! And mark my words!!! I still didn't get any better results!

For Future Reference: OpenCV's documentation is sometimes a bit unclear and imprecise so I would never bet on the tutorials and installation guideline that they are providing. IF ANYONE IS READING THIS AS CORE OPENCV CONTRIBUTOR, I APOLOGISE BUT IT IS REALLY TRUE! ALL YOUR ONLINE DOCUMENTATION NEEDS TO BE QUALITATIVELY IMPROVED.

Try this (It will also work for 2.2, 2.3, 2.4.2 and (I tried it with OpenCV 2.4.3 (SVN trunk)!! http://www.aishack.in/2010/03/installing-and-configuring-opencv-2-0-on-windows/ BUT...make sure that you add the build/bin/debug and build/bin/release folders to the Additional Library Directories (in Linker > GENERAL and VC++ Directories in your DEBUG and RELEASE Configuration Property Sheet). Make sure that you copy and paste the .dll files FROM the build/bin/debug folder INTO YOUR SOLUTION'S (NOT PROJECT'S) DEBUG AND RELEASE folders. Do the same for the build/bin/release folder, BUT COPY THE .DLLs ONLY TO YOUR SOLUTIONS'S RELEASE FOLDER, NOT DEBUG.

One good thing is that having the DEBUG AND RELEASE DLLs in both DEBUG and RELEASE folders of your solutions ACTUALLY DOESN'T BREAK your code!! Those dlls are pretty much same in DEBUG and RELEASE configuration, may be few different macros and stuff!! At least, it didn't cause any trouble in my own code!!

Try this and see if it works :)!