-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
tesseract/4.1.1: libarchive dep and portable build #4278
tesseract/4.1.1: libarchive dep and portable build #4278
Conversation
Failure in build 1 (
|
Some configurations of 'tesseract/4.1.1' failed in build 2 (
|
Some configurations of 'tesseract/4.1.1' failed in build 3 (
|
All green in build 4 (
|
# required for 5.0 | ||
tools.rmdir(os.path.join(self.package_folder, 'lib', 'cmake')) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's no 5.0 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was experimenting in packaging 5.0.x-alpha. Of course, I can drop it now and add for the final version.
Co-authored-by: Chris Mc <[email protected]>
All green in build 5 (
|
All green in build 6 (
|
I was just wondering why the tesseract lib can be compiled at all on CCI for macOS (CCI uses all apple-clang versions in C++03 mode 🤨). https://github.com/tesseract-ocr/tesseract/pull/643/files It's really a matter of luck with which c++ standard the libs are built. |
tesseract uses a clever introspection for C++ 11/14/17 and uses the latest supported standard supported by a compiler. There is no minimum required standard anywhere. If a compiler has C++-XY features, they will be enabled via |
All green in build 7 (
|
Specify library name and version: tesseract/4.1.1
conan-center hook activated.
Changes: