vzyubin

2 Luo Feng: It seems to me to use the tools you need NI-Vision and then Run-Time-Engine with the IMAQ-abilities (that demands the non-free license).

Well as you go on with this project you will soon find that it takes A LOT of time and effort to write such a thing, and therefore it is likely that your Open Source library is only ever going to support a fraction of the functionality of IVision and you will understand why they didn't make the entire OpenCV API fully accessible in LabVIEW. IVision as it is, is a really large task in itself to accomplish already and contains quite a bit of work to make the OpenCV API work with good performance from LabVIEW. Sure you could go and simply create LabVIEW wrapper VIs for the OpenCV functions directly without any intermediate DLL but you will soon find out that the VIs created in such a way are kind of hard to develop and maintain and the performance of such a solution is likely going to suffer.

1. I have heard, tests show, IMAQ-functions have the perfomance problems comparing to OpenCV (from 1.5 up to 10 times)

2. It seems to me we need:

a) a several base functions that solve low level incompatibility problem OpenCV-LabVIEW

b) dll-s of OpenCV functions

c) a short manual that explanes how to wrap new OpenCV function

So, everybody can wrap the functions in need. Obiously, for a lot of simple projects that assume mass yielding it can be the best way to go.

Best wishes,