MIRRORS/poky
1
0
Fork 0
mirror of git://git.yoctoproject.org/poky.git synced 2025-07-19 21:09:03 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity
23,728 Commits 39 Branches 594 Tags 250 MiB
Python 53.7%
BitBake 12.7%
HTML 10.9%
Roff 6.2%
Pawn 3.6%
Other 12.3%
fe240006fb
Go to file
Laurentiu Palcu fe240006fb qemuwrapper: use fallback in case the ELF binary is wrong 
This wrapper script is called mainly from intercept hooks and allarch
packages postinstalls. When multilib is used, the qemuwrapper script
points to the binary that matches the MACHINE architecture.

For example: if MACHINE=qemux86_64 and we activate multilib, then the
postinstalls for lib32 packages would call qemu-x86_64 with 32 bit
binaries and they would certainly fail.

This patch adds just a fallback method if the exit code of the previous
qemu call corresponds to "Invalid ELF image for this architecture"
error. This will allow us to have all postinstalls run on host.

(From OE-Core rev: 0c6ddb84043f0f917543cdaf4814efc15cd0273f)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-29 14:45:09 +01:00
bitbake bitbake: data: fix performance regression 2013-04-15 15:57:31 +01:00
documentation dev-manual: Fixed directory name used in example. 2013-04-17 22:34:23 +01:00
meta qemuwrapper: use fallback in case the ELF binary is wrong 2013-04-29 14:45:09 +01:00
meta-hob meta-*/conf/layer.conf: tweak BBFILES comment 2013-04-10 09:23:17 +01:00
meta-skeleton hello-mod: Ensure the produced package name begins with kernel-module- 2013-04-13 23:50:59 +01:00
meta-yocto poky.conf: add Poky 1.4 and CentOS 6.4 to SANITY_TESTED_DISTROS 2013-04-15 17:21:28 +01:00
meta-yocto-bsp routerstationpro: move board off 3.4 and onto the 3.8 kernel 2013-04-28 12:12:21 +01:00
scripts scripts/contrib/build-perf-test.sh: change the global results format 2013-04-29 14:45:07 +01:00
.gitignore gitignore: only ignore meta- directories 2013-01-15 08:12:01 +00:00
LICENSE LICENSE: Clarify the license recipe source code is under 2010-06-10 10:13:18 +01:00
oe-init-build-env oe-init-build-env: Make it use the correct $OEROOT with zsh 2013-04-05 23:05:34 +01:00
README README: Clarify where to send patches 2012-08-22 14:05:00 +01:00
README.hardware README.hardware: Update mpc8315 load address 2013-04-16 12:13:33 +01:00

README

Poky

Poky is an integration of various components to form a complete prepackaged build system and development environment. It features support for building customised embedded device style images. There are reference demo images featuring a X11/Matchbox/GTK themed UI called Sato. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK with IDE integration.

Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of layers which extend the systems capabilities in a modular way.

As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information e.g. for the hardware support. Poky is in turn a component of the Yocto Project.

The Yocto Project has extensive documentation about the system including a reference manual which can be found at: http://yoctoproject.org/documentation

OpenEmbedded-Core is a layer containing the core metadata for current versions of OpenEmbedded. It is distro-less (can build a functional image with DISTRO = "") and contains only emulated machine support.

For information about OpenEmbedded, see the OpenEmbedded website: http://www.openembedded.org/

Where to Send Patches

As Poky is an integration repository, patches against the various components should be sent to their respective upstreams.

bitbake: bitbake-devel@lists.openembedded.org

meta-yocto: poky@yoctoproject.org

Most everything else should be sent to the OpenEmbedded Core mailing list. If in doubt, check the oe-core git repository for the content you intend to modify. Before sending, be sure the patches apply cleanly to the current oe-core git repository. openembedded-core@lists.openembedded.org

Note: The scripts directory should be treated with extra care as it is a mix of oe-core and poky-specific files.