Wang Mingyu
1c28d5d850
Changelog: ============ * Set hOCR capabilities ocrp_dir and ocrp_lang unconditionally. * Calculate row bounding box in single-word mode per (issue #4304). * Reduce clock syscalls (#4303). * Several small performance and other code fixes. * Modernized code. * Print time for tessedit_timing_debug in milliseconds. * Print time for ErrorCounter::ComputeErrorRate in milliseconds. * cmake: Correctly set the soversion based on SemVer properties. * Do not export PDBs for static libraries (issue #4279). * Several other small fixes and improvements for builds and CI. * Modernize code for renderers and remove filename conversion for Windows (#4330). * Add build rule for Windows installer. * Support symbolic values for --oem and --psm options. * Remove Tensorflow support. * Add RISC-V V support (#4346). * Remove broken GitHub action msys2-4.1.1. Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
layer maintainer: Khem Raj raj.khem@gmail.com