I've zipped up the project and put it at

http://www.velocraptor.com/downloads/ocropus-0.4-mac-build.zip

I think the structure should be reasonably obvious - it needs the
source of the dependencies filled into the holes. I ran configure,
then make, for each, but not make install, so that the xcode project
then takes the libs from where they are built.

I don't have the 0.3 build in anything like as convenient a form I'm
afraid.

Be sure to let me know if you get results

Cheers

Duncan

On Jun 8, 12:04 pm, Max MacLeod <[email protected]> wrote:
> Hi Duncan,
> I'd be very interested to have a look at the XCode project. Would you have
> 0.3 available also?
>
> I can get it to build and compile fine, and it runs the Lua commands also.
>
> When I try and test it with an image it takes ages then comes back with a
> bus error.
>
> Cheers,
> Max
>
> 2009/6/7 [email protected] <[email protected]>
>
>
>
> > I have a build on Mac OS (10.5) that I'm happy to share with anyone. I
> > built the dependencies (libtiff, gsl etc) with configure and make, and
> > then iulib and ocropus with XCode. One of my reasons for this strategy
> > is that I am a keen never to 'make install', so that I have a self-
> > contained distribution (VelOCRaptor is a Mac GUI app).
>
> > Drop me a line and I will ship either the binaries or the XCode
> > project. I haven't published more formally because, given that I have
> > lots of instances of issue 160, I wonder if the resulting build is
> > flawed in some way.
>
> > Cheers
>
> > Duncan
> >www.VelOCRaptor.com- Simple Affordable Mac OCR
>
> > PS - BTW Tom - I notice that issue 160 has been closed - I am still
> > seeing it.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to