The Matlab code generator is fully integrated into the OpenCV build system. If cmake finds a Matlab installation available on the host system while configuring OpenCV, it will attempt to generate Matlab wrappers for all OpenCV modules. If cmake is having trouble finding your Matlab installation, you can explicitly point it to the root by defining the `MATLAB_ROOT_DIR` variable. For example, on a Mac you could type:
The Matlab code generator is fully integrated into the OpenCV build system. If cmake finds a Matlab installation available on the host system while configuring OpenCV, it will attempt to generate Matlab wrappers for all OpenCV modules. If cmake is having trouble finding your Matlab installation, you can explicitly point it to the root by defining the `MATLAB_ROOT_DIR` variable. For example, on a Mac you could type:
@ -44,7 +44,7 @@ to get help on the purpose and call signature of a particular method, or
to get general help regarding the OpenCV bindings. If you ever run into issues with the bindings
to get general help regarding the OpenCV bindings. If you ever run into issues with the bindings
cv.buildInformation();
cv.buildInformation();
will produce a printout of diagnostic information pertaining to your particular build of OS, OpenCV and Matlab. It is useful to submit this information alongside a bug report to the OpenCV team.
will produce a printout of diagnostic information pertaining to your particular build of OS, OpenCV and Matlab. It is useful to submit this information alongside a bug report to the OpenCV team.
@ -158,9 +158,9 @@ Attempt to compile a simple definition using the mex compiler. A mex file is act
If any of the configure time tests fail, the bindings will be disabled, but the main OpenCV configure will continue without error. The configuration summary will contain the block:
If any of the configure time tests fail, the bindings will be disabled, but the main OpenCV configure will continue without error. The configuration summary will contain the block:
Matlab
Matlab
mex: /Applications/MATLAB_R2013a.app/bin/mex
mex: /Applications/MATLAB_R2013a.app/bin/mex
compiler/generator: Not working (bindings will not be generated)
compiler/generator: Not working (bindings will not be generated)
**Generate the sources (build)**
**Generate the sources (build)**
Given a set of modules (the intersection of the OpenCV modules being built and the matlab module optional dependencies), the `CppHeaderParser()` from `opencv/modules/python/src2/hdr_parser.py` will parse the module headers and produce a set of definitions.
Given a set of modules (the intersection of the OpenCV modules being built and the matlab module optional dependencies), the `CppHeaderParser()` from `opencv/modules/python/src2/hdr_parser.py` will parse the module headers and produce a set of definitions.
@ -174,18 +174,18 @@ The `ParseTree()` from `opencv/modules/matlab/generator/parse_tree.py` takes thi
The equivalent refactored output will look like:
The equivalent refactored output will look like:
```python
```python
Function
Function
name = 'fill'
name = 'fill'
rtype = 'void'
rtype = 'void'
static = True
static = True
req =
req =
Argument
Argument
name = 'mat'
name = 'mat'
type = 'cv::Mat'
type = 'cv::Mat'
ref = '&'
ref = '&'
I = True
I = True
O = True
O = True
default = ''
default = ''
```
```
The added semantics (Namespace, Class, Function, Argument, name, etc) make it easier for the templating engine to parse, slice and populate definitions.
The added semantics (Namespace, Class, Function, Argument, name, etc) make it easier for the templating engine to parse, slice and populate definitions.
@ -262,27 +262,27 @@ File Reference
**gen_matlab.py**
**gen_matlab.py**
gen_matlab has the following call signature:
gen_matlab has the following call signature:
gen_matlab.py --hdrparser path/to/hdr_parser/dir
gen_matlab.py --hdrparser path/to/hdr_parser/dir
--rstparser path/to/rst_parser/dir
--rstparser path/to/rst_parser/dir
--moduleroot path/to/opencv/modules
--moduleroot path/to/opencv/modules
--modules core imgproc highgui etc
--modules core imgproc highgui etc
--extra namespace=/additional/header/to/parse
--extra namespace=/additional/header/to/parse
--outdir /path/to/place/generated/src
--outdir /path/to/place/generated/src
**build_info.py**
**build_info.py**
build_info has the following call signature:
build_info has the following call signature:
build_info.py --os operating_system_string
build_info.py --os operating_system_string
--arch bitness processor
--arch bitness processor
--compiler id version
--compiler id version
--mex_arch arch_string
--mex_arch arch_string
--mex_script /path/to/mex/script
--mex_script /path/to/mex/script
--cxx_flags -list -of -flags -to -passthrough
--cxx_flags -list -of -flags -to -passthrough
--opencv_version version_string
--opencv_version version_string
--commit commit_hash_if_using_git
--commit commit_hash_if_using_git
--modules core imgproc highgui etc
--modules core imgproc highgui etc
--configuration Debug/Release
--configuration Debug/Release
--outdir path/to/place/build/info
--outdir path/to/place/build/info
**parse_tree.py**
**parse_tree.py**
To build a parse tree, first parse a set of headers, then invoke the parse tree to refactor the output:
To build a parse tree, first parse a set of headers, then invoke the parse tree to refactor the output:
hbristow
12 years ago