generic-poky

OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705

Go to file

Mikko Rapeli 4490625088 bitbake: bitbake: Fix return value checks from subprocess.call()'s Python function subprocess.call() returns the return value of the executed process. If return values are not checked, errors may go unnoticed and bad things can happen. Change all callers of subprocess.call() which do not check for the return value to use subprocess.check_call() which raises CalledProcessError if the subprocess returns with non-zero value. https://docs.python.org/2/library/subprocess.html#using-the-subprocess-module All users of the function were found with: $ git grep "subprocess\.call" \| \ egrep -v 'if.subprocess\.call\|=\ +subprocess\.call\|return.subprocess\.call' Tested similar patch on top of yocto jethro. Only compile tested core-image-minimal on poky master branch. (Bitbake rev: aac956a0950c05bf58af1885474cd89bb9c8fbd1) Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2017-11-05 22:37:29 +00:00
bitbake	bitbake: bitbake: Fix return value checks from subprocess.call()'s	2017-11-05 22:37:29 +00:00
documentation	ref-manual: Fixed broken link.	2017-09-02 00:52:57 +01:00
meta	goarch.bbclass: Replace logic for setting GOARM	2017-10-24 14:55:01 +01:00
meta-poky	poky: Update version to 2.3.2	2017-09-11 22:16:59 +01:00
meta-selftest	wic-image-minimal: stop using core-image-minimal	2017-04-12 15:09:58 +01:00
meta-skeleton	useradd-example: exclude from world	2017-01-09 13:39:11 +00:00
meta-yocto/conf	meta-yocto: Rename to meta-poky to better match its purpose	2016-02-28 11:31:17 +00:00
meta-yocto-bsp	linux-yocto/4.1: generix86* bsp fix perf issue with gcc >=7	2017-09-21 17:19:25 +01:00
scripts	recipetool: git reformat URI mangling & parameter stripped	2017-07-27 22:36:45 +01:00
.gitignore	add !meta-poky to .gitignore file	2016-03-26 08:06:58 +00:00
.templateconf	meta-yocto: Rename to meta-poky to better match its purpose	2016-02-28 11:31:17 +00:00
LICENSE	Fix license notices for OE-Core	2014-01-02 12:58:54 +00:00
README	meta-yocto: Rename to meta-poky to better match its purpose	2016-02-28 11:31:17 +00:00
README.hardware	README.hardware: update MPC8315E-RDB section	2017-01-16 18:08:20 +00:00
oe-init-build-env	oe-init-build-env*: Make them actually return failures	2016-03-20 23:12:30 +00:00
oe-init-build-env-memres	oe-init-build-env*: Make them actually return failures	2016-03-20 23:12:30 +00: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 = "nodistro") 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 (built using a tool called combo-layer),
patches against the various components should be sent to their respective
upstreams:

bitbake:
    Git repository: http://git.openembedded.org/bitbake/
    Mailing list: bitbake-devel@lists.openembedded.org

documentation:
    Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
    Mailing list: yocto@yoctoproject.org

meta-poky, meta-yocto-bsp:
    Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp)
    Mailing list: poky@yoctoproject.org

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.

    Git repository: http://git.openembedded.org/openembedded-core/
    Mailing list: 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.