cmusatyalab / diamond-core-filters Goto Github PK

Currently during make I'm getting:

./include/lib_ocvimage.h:31:23: fatal error: opencv/cv.h: No such file or directory

which I'd expect ./configure to catch?

Same as in #4, unexpected install location is:

./x86_64-linux-gnu/libjpeg.a

Imported from Bugzilla. This issue originally by agoode at 2009-05-26 13:33:30 -0400.

The DOG texture filter in SnapFind has a bug in it. This was fixed in 44acfec and reverted in f211ddd. Why does this buggy code work so well? What is it doing? How could we exploit it?

Getting this with ./configure:

configure: error: Missing libtiff.a: try using --with-staticlib option

My libtiff.a appears here:

➜ lib find . -name '*libtiff*'
...
./x86_64-linux-gnu/libtiff.a
...

but the configure script appears to by default search the wrong locations (upstream issue?):

stat("/opt/diamond-filter-kit/lib/libtiff.a", 0x7ffff218e390) = -1 ENOENT (No such file or directory)
stat("/usr/lib/libtiff.a", 0x7ffff218e390) = -1 ENOENT (No such file or directory)
stat("/lib/libtiff.a", 0x7ffff218e390)  = -1 ENOENT (No such file or directory)

Since fil_thumb only scales by integer factors, it often produces thumbnails smaller than requested in both dimensions. This causes inefficient use of screen real estate in the search application.