Quote:
Originally Posted by Gertjan
Yes, it should work like the PDF plugin. I planned to pull your plugin through a debugger to see what's happening, but ran into some issue cross-compiling the djvu libraries. I'll try later, unless someone can provide binaries.
|
Here are some binaries, created using the latest DR1000 SDK with:
tar -xzvf djvulibre-3.5.22.tar.gz
cd djvulibre-3.5.22
./configure --host=arm-poky-linux-gnueabi --prefix=/usr
make
make install DESTDIR=/home/user/djvulibre
cd /home/user/djvulibre
tar -czf djvulibre-dr1000-bin.tar.gz usr
if you have installed the poky toolchain in the location described in the documentation, install with:
sudo tar -xzvf djvulibre-dr1000-bin.tar.gz -C /usr/local/poky/eabi-glibc/arm/arm-poky-linux-gnueabi/
then compiled the plugin using:
tar -xzvf djvu-plugin-src-0.1.4pre.tar.gz
cd djvu-plugin
autoreconf --install
./configure --host=arm-poky-linux-gnueabi --enable-debug
make
This does result in some error about creating libuds-plugin-djvu.la, because there seems to be something wrong with the location of libjpeg in /usr/local/poky/eabi-glibc/arm/arm-poky-linux-gnueabi/usr/lib/libdjvulibre.la. The .so file is created anyway, so I didn't bother to fix this. the directory plugin_impl/.libs should contain the required libuds-plugin-djvu.so now. I haven't tested 'make install' functionality for the plugin, because my own scripts directly copy this file to /usr/lib/uds in the emulator. If you have run the installer script from binary release 0.1.3, you should have the other required files on the emulator already.
I hope this is what you need. Note that this is all built using the 1.7 SDK and emulator. The interfaces for the DR800 (and possibly the latest DR1000 firmware as well) are slightly different, so it will probably not load if you use a newer version.
Quote:
I hope you understand that, although we're willing, we have limited resources to support community efforts. We don't want to delay all those wonderful new features we're working on. 
|
Yes I understand, I really appreciate your help. I didn't expect that you needed to compile or run it at all. When you said something about the plugin reporting whether to use the low level interface, I thought that it would be something along the lines of an easy single line change. Perhaps I was being a bit too optimistic
By the way, my guess is that if you remove .pdf from the hardcoded extensions in uds, it will also try to load the pdf plugin using this code path and it will fail in exactly the same way. It's just a guess, but you may not need to compile the djvu plugin after all to see what is wrong.