Include folder structure: opencv and/or opencv2?

edit

Hi Martin,

Thanks muchly for your help!

The C function / C++ function schism sounds like a plausible explanation for the file structure. Unless anyone proposes a different explanation, then I'll mark your answer as 'correct' :)

Regarding dragging and dropping files... I am trying to make use of some opencv functions to get / process images from a webcam. The bulk of the project will be my own code. I've made a folder called "lib" in my solution directory and copied relevant opencv (and other 3rd party) libraries into that. This copying was the 'drag and drop' that I alluded to. The actual include is done properly within the VS2010 options.

Would you still use CMake, in this context? I've previously used it to build openCV, but am not sure how to use it to manage include files..

Hi Zadacka, In the end the choice on how to build your projects is entirely yours, if you are comfortable with that approach and you don't foresee any problems with it then it is OK. Personally, always use CMake to generate my projects because it is very flexible and portable. With a CMakeLists.txt as simple as this:

cmake_minimum_required( VERSION 2.6 FATAL_ERROR)

project ( my_project )

find_package(OpenCV 2.4 REQUIRED)

find_package(OtherLibrary REQUIRED)

add_executable (my_executable my_source1.cpp my_source2.cpp ...) target_link_libraries(my_executable ${OpenCV_LIBS} ${OtherLibrary_LIBS})

You can generate project files for VS2012, Eclipse, Unix Makefiles, etc... But, as I said, this is just a suggestion, how you build your projects is entirely your call.