From the source code available at the Github repository, what needs to be compiled is the C++ module located inside the src/imgSeekLib directory (called from now on imgdb). Here are some instructions.
Linux: Compile running the command “python setup.py build” (from inside the src/imgSeekLib directory)
Windows: Open the imgdb solution under the imgdb-msvc and compile it. You may need to adjust the include and libraries dir for the solution to point to the correct locations of Python, Java (if you want the Java bindings) and ImageMagick.
The output of this compilation process are the files _imgdb.pyd (Windows) or imgdb.so (Unix) which are dynamic libraries that after compilation is finished, must be placed on the imgSeekLib directory of both isk-daemon and imgSeek.
First, get the source code for the Subversion repository:
Inside the checked out module there is a src/net/imgseek/imgdb/core directory. From inside it, invoke the build script:
If all goes well you should find the newly compiled _imgdb.so library somewhere deep under the build directory. The resulting dynamic libraries (imgdb.so/pyd) should then replace the original version from the official isk-daemon distribution (located inside the imgSeekLib dir).
Sometimes the .so library is created without a leading underscore. If starting isk-daemon doesn’t work, try renaming the .so file and prefix it with an underscore so it looks like “_imgdb.so”. The error message in this case looks like this:
Inside the checked out module there is a imgdb-msvc directory. Inside this directory you can find a Microsoft Visual C++ Express (free download from MS) solution file.
Open and build it. You may need to setup linking options (additional library dirs) to tell MSVC where to find the ImageMagick and Pythons libraries and development headers.
Please use one of the mailing lists if you run into any trouble.