This forum is disabled, please visit https://forum.opencv.org
 | 1 | initial version |
OpenCV v3.3.1 -- don't waste any time with that. if you want to contribute something, you have to work with latest master
Making OpenCV_videoio.cpp as startup project -- you will need test_main.cpp (as a minimum), too. also you have to link opencv_ts340.lib (do you have it ?) and have opencv/ts/imclude/opencv2 in your "additional include path"
in Command Line, that too without my knowledge it closes, as it is finished -- yes that's expected. rather run it from a cmd, than from your ide.
is there any excel sheet saved -- nope.
| | 2 | No.2 Revision |
OpenCV v3.3.1 -- don't waste any time with that. if you want to contribute something, you have to work with latest master
Making OpenCV_videoio.cpp as startup project -- you will need test_main.cpp (as a minimum), too. also you have to link opencv_ts340.lib (do you have it ?) and have opencv/ts/imclude/opencv2opencv/ts/include in your "additional include path"
in Command Line, that too without my knowledge it closes, as it is finished -- yes that's expected. rather run it from a cmd, than from your ide.
is there any excel sheet saved -- nope.
| | 3 | No.3 Revision |
OpenCV v3.3.1 --
don't waste any time with that. if you want to contribute something, you have anything, you have to work with latest master
Making OpenCV_videoio.cpp as startup project
well, usually the unit tests get built along with the libs, so you're expected to build the opencv libs locally, with cmake -DBUILD_TESTS=ON, which will generate project -- files for the tests, too, so you can just choose the videoio one for your startup project.
however, it somehow sounds, like you wanted to use the prebuilt libs, and make a new project for this. then you will need test_main.cpp (as a minimum), minimum, better add the whole folder), too. also you have to link opencv_ts340.lib (do you have it ?) and have opencv/ts/include in your "additional include path"
in Command Line, that too without my knowledge it closes, as it is finished --
yes that's expected. rather run it from a cmd, than from your ide.
is there any excel sheet saved --
nope.
| | 4 | No.4 Revision |
OpenCV v3.3.1
don't waste any time with that. if you want to contribute anything, you have to work with latest master
I would like to Know, how to run this test case?
it's just an exe, like any other opencv program. (though iirc they don't come prebuilt with the binary distribution)
Making OpenCV_videoio.cpp as startup project
well, usually the unit tests get built along with the libs, so you're expected to build the opencv libs locally, with cmake -DBUILD_TESTS=ON, which will generate project files for the tests, too, so you can just choose the videoio one for your startup project.
however, it somehow sounds, like you wanted to use the prebuilt libs, and make a new project for this. then you will need test_main.cpp (as a minimum, better add the whole folder), too. also you have to link opencv_ts340.lib (do you have it ?) and have opencv/ts/include in your "additional include path"
in Command Line, that too without my knowledge it closes, as it is finished
yes that's expected. rather run it from a cmd, than from your ide.
is there any excel sheet saved
nope.
| | 5 | No.5 Revision |
OpenCV v3.3.1
don't waste any time with that. if you want to contribute anything, you have to work with latest master
I would like to Know, how to run this test case?
it's just an exe, like any other opencv program. (though iirc they don't come prebuilt with the binary distribution)
Making OpenCV_videoio.cpp as startup project
well, usually the unit tests get built along with the libs, so you're expected to build the opencv libs locally, with cmake -DBUILD_TESTS=ON, which will generate project files for the tests, too, so you can just choose the videoio one for your startup project.
however, it somehow sounds, like you wanted to use the prebuilt libs, and make a new project for this. then you will need test_main.cpp (as a minimum, better add the whole folder), too. also you have to link opencv_ts340.lib (do you have it ?) and have opencv/ts/include in your "additional include path"
in Command Line, that too without my knowledge it closes, as it is finished
yes that's expected. rather run it from a cmd, than from your ide.
is there any excel sheet saved
nope.
| | 6 | No.6 Revision |
OpenCV v3.3.1
don't waste any time with that. if you want to contribute anything, you have to work with latest master
I would like to Know, how to run this test case?
it's just an exe, like any other opencv program. (though iirc they don't come prebuilt with the binary distribution)
you would either run all tests by calling test_videoio or specific, single ones by calling test_videoio --gtest_filter=videoio/Videoio_Bunny.read_position/0
Making OpenCV_videoio.cpp as startup project
well, usually the unit tests get built along with the libs, so you're expected to build the opencv libs locally, with cmake -DBUILD_TESTS=ON, which will generate project files for the tests, too, so you can just choose the videoio one for your startup project.
however, it somehow sounds, like you wanted to use the prebuilt libs, and make a new project for this. then you will need test_main.cpp (as a minimum, better add the whole folder), too. also you have to link opencv_ts340.lib (do you have it ?) and have opencv/ts/include in your "additional include path"
in Command Line, that too without my knowledge it closes, as it is finished
yes that's expected. rather run it from a cmd, than from your ide.
is there any excel sheet saved
nope. opencv's buildbots run python scripts which generate reports e.g. here
