1*4882a593Smuzhiyunmeta-oe 2*4882a593Smuzhiyun======= 3*4882a593Smuzhiyun 4*4882a593SmuzhiyunThis layer depends on: 5*4882a593Smuzhiyun 6*4882a593SmuzhiyunURI: git://github.com/openembedded/openembedded-core.git 7*4882a593Smuzhiyunbranch: kirkstone 8*4882a593Smuzhiyun 9*4882a593Smuzhiyunluajit recipe requires host compiler to be able to generate 32bit code when target is 32bit 10*4882a593Smuzhiyune.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed 11*4882a593Smuzhiyunpackages to fullfit this might have different names on different host distributions 12*4882a593Smuzhiyune.g. on archlinux based distributions install prerequisites like below 13*4882a593Smuzhiyun 14*4882a593Smuzhiyunpacman -S lib32-gcc-libs lib32-glibc 15*4882a593Smuzhiyun 16*4882a593SmuzhiyunUbuntu 17*4882a593Smuzhiyunsudo apt-get install gcc-multilib linux-libc-dev:i386 18*4882a593Smuzhiyun 19*4882a593SmuzhiyunSend pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][kirkstone]' in the subject' 20*4882a593Smuzhiyun 21*4882a593SmuzhiyunWhen sending single patches, please use something like: 22*4882a593Smuzhiyun'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][kirkstone][PATCH"' 23*4882a593Smuzhiyun 24*4882a593SmuzhiyunYou are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded 25*4882a593Smuzhiyunto share your patches, this is preferred for patch sets consisting of more than one patch. 26*4882a593Smuzhiyun 27*4882a593SmuzhiyunOther services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 28*4882a593Smuzhiyun'git fetch <remote>' works the same on all of them. We recommend GitHub because it is free, easy 29*4882a593Smuzhiyunto use, has been proven to be reliable and has a really good web GUI. 30*4882a593Smuzhiyun 31*4882a593Smuzhiyunlayer maintainer: Armin Kuster <akuster808@gmail.com> 32