Files
meta-openembedded/meta-oe
Martin Jansa 8289b8df7f mozjs: use PV in MULTILIB_SCRIPTS
* to avoid possible issue next time new mozjs version recipe is
  introduced (as multilib isn't as well tested as other build configs)

* this depends on oe-core change to expand script name in MULTILIB_SCRIPTS:
  https://lists.openembedded.org/g/openembedded-core/message/188301

Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 7d473b7616)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
2023-10-04 07:52:48 -07:00
..
2023-08-15 14:24:44 -07:00
2023-09-20 15:34:02 -07:00
2023-09-20 15:34:02 -07:00
2023-09-20 22:15:39 -07:00

meta-oe

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git branch: nanbield

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][nanbield]' 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][nanbield][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 ' 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: Armin Kuster akuster808@gmail.com