On Wednesday 29 July 2009 20:18:33 tmbdev wrote: > You shouldn't need Tesseract for OCRopus 0.4 and higher, since the > Tesseract bindings have been moved out of OCRopus into a separate > project, ocrotess. You can find that here: > > http://iupr1.cs.uni-kl.de/cgi-bin/hgwebdir.cgi > > They integrate at the command line. Starting with 0.5, they will > hopefully also be available as dynamically loadable components. OK, so lets see if I understand this correctly.
There are five hg trees: 1. iulib 2. ocropus 3. ocrotess 4. ocroswig 5. ocrofst [there was previously a ocroscript repository too, but that became ocroswig] To get them, we need to: 1. hg clone http://iulib.googlecode.com/hg iulib 2. hg clone http://ocropus.googlecode.com/hg ocropus 3. hg clone http://iupr1.cs.uni-kl.de/cgi-bin/hgwebdir.cgi/ocrotess/ 4. hg clone http://iupr1.cs.uni-kl.de/cgi-bin/hgwebdir.cgi/ocroswig/ 5. hg clone http://iupr1.cs.uni-kl.de/cgi-bin/hgwebdir.cgi/ocrofst/ iulib depends on a range of image I/O libs (libpng, libjpeg, libtiff and probably libpoppler in the long term) and some SDL libs, plus ffmeg. ocropus depends on iulib, and OpenMP and GSL. There are currently some checks for other things (leptonica, tesseract, image I/O libs and SDL) but they can probably be removed as things have been split off, and once we have proper libtool / shared object linking. ocrotess depends on leptonica and tesseract, as well as ocropus and iulib. ocroswig depends on pretty much everything above. ocrofst depends on iulib (and some FST package?) How close it that? Brad --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
