Hello Sun,
I am afraid that I cannot help you much with the work, because I am just a scientist who learned enough programming for somehow getting an image processing algorithm for microscopy image analysis run, and I have not enough programming knowledge to understand how MATLAB, JULIA, openCV, JAVA, PYTHON, etc. work under the hood and how those wrappers, bindings, APIs, etc., are (to be) implemented. The only feedback I could give is to share some links concerning the new openCV bindings for MATLAB, which now can become automatically generated when openCV3 is installed on a computer where a MATLAB installation is already located. Maybe, following those links, you can see how that is done, and maybe get in contact with the creators of that "automatic bindings generator". I would guess that the concept backing up the MATLAB bindings generator could be copied to become the indentical concept for a JULIA bindings generator, as well? Then, whenever openCV would move on to new things, in the future, then any requested change to that concept would in principal only have to be solved once: "only" the final coding for the MATLAB or JULIA branch would differ. Maybe the concept in use for the MATLAB bindings generation is the identical concept used also to generate teh JAVA bindings? For sure, the creators of those generators over at openCV.org would know!
The project home is:
Somebody comments here somehting about the underlaying concept:
All the best! Robert.