mirror of
https://github.com/thead-yocto-mirror/meta-openembedded
synced 2026-09-10 08:04:56 +02:00
According to wiki more than 1300 printer drivers. Specifically the CUPS dye-sublimation backend, used in industrial and medical is a nice fit when using Yocto for embedded solutions targeting this segment. As the gutenprint code generate a tool for string management, the native recipe is designed to just create the output from this tool (a header file). So the cross compatible version is depending on native version. Thought about using BBCLASSEXTEND instead of separate files. Though as the purpose of the two recipes is different (one for generating header file, the other for generating the actual lib) and different dependencies I decided to keep it as two recipes. Signed-off-by: Claus Stovgaard <clst@ambu.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. Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch <remote>' 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>