Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac OSX support #27

Open
zeasy opened this issue Apr 25, 2014 · 10 comments
Open

Mac OSX support #27

zeasy opened this issue Apr 25, 2014 · 10 comments

Comments

@zeasy
Copy link

zeasy commented Apr 25, 2014

No description provided.

@diimdeep
Copy link

diimdeep commented Jul 8, 2014

I have same question ! If not, why not? I think it should because it is present in cocapods

@ws233
Copy link
Collaborator

ws233 commented Oct 1, 2014

You are free to port it to mac and provide a pull request with your changes.

@3a4oT
Copy link

3a4oT commented Dec 2, 2014

is any tutorial or examples exist, how port to mac?

@zachberger
Copy link
Collaborator

tesseract-ocr the upstream c++ library and engine is supported on Mac and is available in macports. A discussion on why this project, an obj-c wrapper, currently doesn't work is being held on #60

@ws233
Copy link
Collaborator

ws233 commented Jan 5, 2015

If we add a mac support, we should change the name of the repo to something like TesseractOCR-objC.
Also, it seems it will take a lot of efforts to port this to mac, but we can try this.

And if we start this, how we should do it?
Use the same code, but insert a lot of define switches like #ifdef target_macos #elseif target_ios #endif
or use different projects for iOS/mac?

@kevincon
Copy link
Collaborator

kevincon commented Jan 5, 2015

Yeah OSX uses AppKit and iOS uses UIKit which seem to use different things for the same name.

For example, UIImage on iOS is actually NSImage on OSX. :(

We could potentially use a #define to create platform-independent strings for some of the incompatibilities. For the image example, we could make #define TESSERACT_IMAGE which could map to NSImage for OSX and UIImage on iOS, then update all the methods to use that.

There might be more severe API incompatibilities we will uncover if we start to do the transition. I think we should wait to work on this until the 4.0.0 release is done so that we have a more stable API to work with before we start analyzing the differences in the two platforms. What do you think?

@ws233
Copy link
Collaborator

ws233 commented Jan 5, 2015

Yup. It's better to postpone this for a while.

@kevincon kevincon changed the title support mac os? Mac OSX support Apr 3, 2015
@mseel
Copy link

mseel commented Dec 23, 2016

any news for Mac OS X support?

Or could someone give me a hint, for getting tesseract in my OS X project?

@tiagosiebler
Copy link

@mseel if you have homebrew, you can install tesseract as a command line option: brew install tesseract --all-languages

@Nododo
Copy link

Nododo commented Nov 20, 2019

watch this and expect good news for a long time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants