-
Notifications
You must be signed in to change notification settings - Fork 857
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically Generated Bindings #290
Comments
http://answers.opencv.org/question/6618/how-python-api-is-generated/ just for reference. |
I don't mean to populate the Issues page here. I'm currently having to wade through the Examples to find ways of doing things. Is there a list of implemented functions? Please see my question here http://stackoverflow.com/questions/34518140/list-of-node-opencv-function-names |
Is there any reason why we couldn't generate Javascript bindings from the same tool, then augment them to add things like async calls and streaming? Has anyone tried this? |
Hi @Queuecumber , here's my effort so far: https://github.com/johncant/opencv/tree/node_bindings Essentially, all I've done so far is copied and pasted bits of cmake involved in the Python bindings generation to get to the point where the node bindings would be generated. My plan is:
|
There's also supposed to be a way of getting OpenCV to compile to Javascript using Emscripten but I can't find any info on it. |
Did you get any further with this @johncant? I like this approach. |
Found this library that seems to generate bindings automatically 🚀 https://github.com/ucisysarch/opencvjs |
Another approach would be to do it similar to the Matlab bindings. This module is very well documented in the official opencv_contrib repository. |
Something I've been looking into for a little while. The OpenCV build process generates python and matlab bindings automatically from the C++ source. One of the issues these JS bindings seem to have is lack of feature support. What do you think about cutting a new version that can do a similar automatic generation for javascript?
Of course this would be very much incompatible with the current JS api, but we would theoretically be able to support most if not all of the features and they would match the C++ api closer
The text was updated successfully, but these errors were encountered: