I downloaded tip on June 14 and finished the build today. This was a
Debian Lenny (stable) system, with Python 2.5. ocropus recommends 2.6.
I had also tried ocropus in 2008 and pieces were still around.
1) I got the package dependencies from the ubuntu-installpackages
scripts. I didn't run the scripts; I just used them for the package
names. Some of these packages came from the Debian multimedia
repository (unofficial); I'm not sure if they are available otherwise.
All the names seemed to be the same.
I may have had to pull some packages from testing/unstable (or go with
older versions). I don't remember.
I didn't use -j4 since I have only one processor; it's hyperthreaded and
so appears to Linux as 2, but I had a feeling it would be faster not to
use the hyperthreading.
2) While building the ocropus project I got:
WARNING: scons not supported on platforms other than Ubuntu 9.10
as I reported previously. Nobody expressed an opinion about this and
things looked OK, so I pressed on.
3) The ocroswig build failed because ocropus.py used the with feature of
Python 2.6. I hacked around this by editing
/usr/local/src/scanner/ocr/ocroswig/build/lib.linux-i686-2.5/ocropus.py
by hand with
from __future__ import with_statement
and reran
sudo python setup.py install
which finally seemed to work.
I don't think that trick will work with Python2.4 or earlier.
I tried adding the from __future__ line into the python code in
ocropus.i, but it ended up in the middle of the file, which is also an
error.
Note that ocropus.py is generated by swig; you can't edit it in advance
of the build. I think manually doing
python setup.py build
edit file
sudo python setup.py install
in place of the make would work (that would skip the initial file
deletion done by the make file).
4) When I tried to run ocropus I discovered I needed to install
python-matplotlib. There might be other python dependencies not listed
in ubuntu-install; I already have numpy installed, for example.
5) The results of building all the modules were a little weird: some of
the files ended up installed to /usr/local, while others went to /usr.
In particular, python modules ended up
in /usr/lib/python2.5/site-packages rather
than /usr/local/lib/python2.5/site-packages.
6)
$ ocropus-pages -h
Traceback (most recent call last):
File "/usr/bin/ocropus-pages", line 13, in <module>
import ocropy
File "/usr/lib/python2.5/site-packages/ocropy/__init__.py", line 4, in
<module>
from ocropus import *
File "/usr/lib/python2.5/site-packages/ocropus.py", line 10, in
<module>
import _ocropus
ImportError: libocropus.so: cannot open shared object file: No such file
or directory
but ocropus page foo.png ran. The former is in /usr/bin, the latter
in /usr/local/bin.
7) I tried ocropus page on a receipt and a medical insurance statement.
It didn't do too well. I realize these are outside of ocropus's target
useage. Unfortunately, they are the primary documents I'm interested
in.
I'd appreciate any pointers on the problems in 6 or 7, or any other
comments.
Ross Boylan
--
You received this message because you are subscribed to the Google Groups
"ocropus" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/ocropus?hl=en.
