This PR should allow the binding code generator to parse and generate flann-related enums.
It checks if modules/flann/include/opencv2/flann.hpp is in the header list, if so (which indicates the user compiles OpenCV with the flann module), it will add modules/flann/include/opencv2/flann/defines.h to the list (if exists, just in case the file is removed or renamed in the future versions of OpenCV).
This should include the following enums and place them in the corresponding modules.
flann_algorithm_t
flann_centers_init_t
flann_log_level_t
flann_distance_t
flann_datatype_t
~For example, flann_algorithm_t will be put in Evision.Flann.FlannAlgorithm:~
Actually Evision.Flann.FlannAlgorithm sounds too wordy lets just remove the prefixed Flann in the module name, so it becomes Evision.Flann.Algorithm.
This PR should allow the binding code generator to parse and generate flann-related enums.
It checks if
modules/flann/include/opencv2/flann.hpp
is in the header list, if so (which indicates the user compiles OpenCV with the flann module), it will addmodules/flann/include/opencv2/flann/defines.h
to the list (if exists, just in case the file is removed or renamed in the future versions of OpenCV).This should include the following enums and place them in the corresponding modules.
flann_algorithm_t
flann_centers_init_t
flann_log_level_t
flann_distance_t
flann_datatype_t
~For example,
flann_algorithm_t
will be put inEvision.Flann.FlannAlgorithm
:~Actually
Evision.Flann.FlannAlgorithm
sounds too wordy lets just remove the prefixedFlann
in the module name, so it becomesEvision.Flann.Algorithm
.Also, let's not add deprecated ones for each of these enums. (See https://github.com/opencv/opencv/blob/39a7b3d1869d31df92029503b9a8670071eac596/modules/flann/include/opencv2/flann/defines.h#L82)