Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would not even attempt to compile the OpenCV source code for an FPGA execution target. There are too many library dependencies and microprocessor architecture oriented assumptions in OpenCV (or in any large microprocessor targeted code base).</p> <p>There are compile-time and run-time libraries on any system. For one example, if we look at the run-time library dependencies of the OpenCV shared library, there are many microprocessor code libraries OpenCV itself uses:</p> <pre><code>dpointer@death:~$ ldd /usr/lib/libcv.so linux-vdso.so.1 =&gt; (0x00007fff1c1ff000) libcxcore.so.4 =&gt; /usr/lib/libcxcore.so.4 (0x00007f03279f7000) libavformat.so.52 =&gt; /usr/lib/libavformat.so.52 (0x00007f0327701000) libavcodec.so.52 =&gt; /usr/lib/libavcodec.so.52 (0x00007f0326ca7000) librt.so.1 =&gt; /lib/librt.so.1 (0x00007f0326a9f000) libz.so.1 =&gt; /lib/libz.so.1 (0x00007f0326888000) libdl.so.2 =&gt; /lib/libdl.so.2 (0x00007f0326683000) libstdc++.so.6 =&gt; /usr/lib/libstdc++.so.6 (0x00007f032636f000) libm.so.6 =&gt; /lib/libm.so.6 (0x00007f03260ec000) libgomp.so.1 =&gt; /usr/lib/libgomp.so.1 (0x00007f0325edd000) libpthread.so.0 =&gt; /lib/libpthread.so.0 (0x00007f0325cc0000) libc.so.6 =&gt; /lib/libc.so.6 (0x00007f032593a000) libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00007f0325722000) libavutil.so.49 =&gt; /usr/lib/libavutil.so.49 (0x00007f0325513000) libbz2.so.1.0 =&gt; /lib/libbz2.so.1.0 (0x00007f0325302000) libgsm.so.1 =&gt; /usr/lib/libgsm.so.1 (0x00007f03250f3000) libschroedinger-1.0.so.0 =&gt; /usr/lib/libschroedinger-1.0.so.0 (0x00007f0324e74000) libspeex.so.1 =&gt; /usr/lib/libspeex.so.1 (0x00007f0324c5a000) libtheora.so.0 =&gt; /usr/lib/libtheora.so.0 (0x00007f0324a0b000) libvorbisenc.so.2 =&gt; /usr/lib/libvorbisenc.so.2 (0x00007f0324630000) libvorbis.so.0 =&gt; /usr/lib/libvorbis.so.0 (0x00007f0324403000) /lib64/ld-linux-x86-64.so.2 (0x00007f03282f1000) liboil-0.3.so.0 =&gt; /usr/lib/liboil-0.3.so.0 (0x00007f0324172000) libogg.so.0 =&gt; /usr/lib/libogg.so.0 (0x00007f0323f6b000) dpointer@death:~$ </code></pre> <p>If you wanted to compile and use OpenCV on an FPGA system, you'd need to compile all of this library code for the FPGA, too. And you'd need an FPGA system run-time environment that would make sure these libraries on the FPGA were available when your code was running on the FPGA system. </p> <p>It's a huge task - you'd have to compile all the libraries OpenCV uses, all the libraries required by those libraries, OpenCV itself, and your top level application code. Oh, and write a run-time environment for your FPGA system. Even if you could compile all of that, it would not fit into an FPGAs resources.</p> <p>On the other hand, you could write your top level C code and any required image processing C code and compile that for an FPGA system. OpenCV source code is an outstanding reference tool for how to implement various image processing algorithms for FPGA targets. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload