laurencedev's profile - activity

Hi @berak, made the FileStorage part via the way you suggested. For the 'xml to char*' one, do you suggest sth. like c

Hi @berak, made the FileStorage part via the way you suggested. For the 'xml to char*' one, do you suggest sth. like c

Hi @berak, made the FileStorage part via the way you suggested. For the 'xml to char*' one, do you suggest sth. like c

We use CascadeClassifier in a demo program, but we don't won't pass the xml file of the classifier directly to others. One way we were trying is to pre-compile the xml's content into the program and use it to instanlized a CascadeClassifier when it runs.

So we found that, through code like the below, the content in a xml can be compiled into the .exe(executable) file, and presented as a const char *. However, the constractors of CascadeClassifier takes either a filename or a FileNode object as a parameter for instanlization, cannot be a char*.

Is there a way to transform a const char * to a FileNode object?

const char *VX =
#include "./models/haarcascade_smile_R.xml"
;

Besides, are there anyother ways to 'hide' the configuration? Make it not so easy to be 'human-readable' as an xml.

char* to FileNode / Hide our XML configurations We use CascadeClassifier in a demo program, but we don't won't pass the

char* to FileNode We use CascadeClassifier in a demo program, but we don't won't pass the xml file of the classifier di

char* to FileNode We use CascadeClassifier in a demo program, but we don't won't pass the xml file of the classifier di

char* to FileNode We use CascadeClassifier in a demo program, but we don't won't pass the xml file of the classifier di

char* to FileNode We use CascadeClassifier in a demo program, but we don't won't pass the xml file of the classifier dir

No similar white list found for WITH_* yet, but all components are list in HERE

Thanks @berak, this is what exact what i am looking for! For others who were confused also: 1. BUILD_LIST is acting lik

Hi, @ak1, thanks for the response. Get some interesting findings on the way you mentioned also. Thanks bro !

Thanks @berak, this is what exact what i am looking for! For others who were confused also: 1. BUILD_LIST is acting lik

Thanks @berak, this is what exact what i am looking for! For others who were confused also: 1. BUILD_LIST is acting lik

Thanks @berak, this is what exact what i am looking for! For other who were confused also: 1. BUILD_LIST is acting like

Thanks @berak, this is what exact what i am looking for! Made some following up findings attached below, in case anyone

We can set the options like the following to compile some but not others:

-DBUILD_opencv_xfeatures2d=ON
-DBUILD_opencv_apps=OFF

As the above, my understanding is xfeatures2d will be compiled (The Makefiles will set it as a target for compilation) and apps definitely not, but other modules haven't specified in the options will be compiled by default. However, if apps is required for xfeatures2d then xfeatures won't be compiled and cmake output will warning this.

What the problems with the above understanding ?

Is there a way to say compile xfeatures2d and the modules it required only ?

Furthermore, is there a way to say compile xfeatures2d and the modules it required and optionally required ones?

How about the WITH options, like -DWITH_1394=OFF, what is the default values for them ? Or, by default, it depends on the environment its running on? For instance, if CMake can find all (local) libraries needed for CUDA, -DWITH_CUDA will be ON by default.

How to set CMake options to compile some modules only? We can set the options like the following to compile some but not

How to set CMake options to compile some modules only? We can set the options like the following to compile some but not

How to set CMake options to compile some modules only? We can set the options like the following to compile some but not

How to set CMake options to compile some modules only? We can set the options like the following to compile some but not

How to set CMake options to compile some modules only? We can set the options like the following to compile some but not

How to set CMake options to compile some modules only? We can set the options like the following to compile some but not

How to set CMake options to compile some modules only? We can set the options like the following to compile some but not

ref http://answers.opencv.org/question/198108/cmake-with-tbb-on-win64-unfamiliar-cmake-gui-fields/for how to enable TBB/

ref https://stackoverflow.com/questions/16767464/how-to-install-opencv-with-tbb-enabled-using-mingw for how to enable TB

Directly cause is no parallel framework has explicitly specified in cmake options. Besides, there is a potential bug i

Failed to run the test of `test_fast.cpp` on Windows with MinGW-W64 Env settings: OS: Windows 10 64bit ToolChain: MinG

Failed to run the test of `test_fast.cpp` on Windows Env settings: OS: Windows 10 64bit ToolChain: MinGW-W64 configure

Failed to run the test of `test_fast.cpp` on Windows Env settings: OS: Windows 10 64bit ToolChain: MinGW-W64 configure

Failed to run the test of `test_fast.cpp` on Windows Env settings: OS: Windows 10 64bit ToolChain: MinGW-W64 configure

Failed to run the test of `test_fast.cpp` on Windows Env settings: OS: Windows 10 64bit ToolChain: MinGW-W64 configure

Failed to run the test of `test_fast.cpp` on Windows Env settings: OS: Windows 10 64bit ToolChain: MinGW-W64 configure

Failed to run the test of `test_fast.cpp` on Windows Env settings: OS: Windows 10 64bit ToolChain: MinGW-W64 configure

Failed to run the test of `test_fast.cpp` Env settings: OS: Windows 10 64bit ToolChain: MinGW-W64 configured with "x86

Failed to run the test of `test_fast.cpp` Env settings: OS: Windows 10 64bit ToolChain: MinGW-W64 configured with "x86

Failed to run the test of `test_fast.cpp` Env settings: OS: Windows 10 64bit ToolChain: MinGW-W64 configured with "x86

Variable `OPENCV_TEST_DATA_PATH` is not recognized in Windows OS Was trying to run some internal tests of OpenCV Contrib

How to set OPENCV_TEST_DATA_PATH in Windows OS Was trying to run some internal tests of OpenCV Contrib. On Linux/Ubuntu,