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

Martin Jansa 258cfa891e python(3): Disable tkinter * restore changes from: http://git.openembedded.org/openembedded-core/commit/?id=53ae544cfdac22c82af452b8c7ebe6664296bd9b * which were shamelessly removed in upgrade to 2.7.9: http://git.openembedded.org/openembedded-core/commit/?id=d4ad95f0d5f08891637c644e85b09da9c4585059 and then spread to python3 as well * fixes following issues reported by test-dependencies WARN: python3: python3-tkinter rdepends on glibc, but it isn't a build dependency? WARN: python3: python3-tkinter rdepends on libpython3, but it isn't a build dependency? WARN: python3: python3-tkinter rdepends on tcl-lib, but it isn't a build dependency? WARN: python: python-tkinter rdepends on glibc, but it isn't a build dependency? WARN: python: python-tkinter rdepends on libpython2, but it isn't a build dependency? WARN: python: python-tkinter rdepends on tcl-lib, but it isn't a build dependency? and following QA warnings in normal builds: python-2.7.11: python-tkinter rdepends on tcl-lib, but it isn't a build dependency, missing tcl in DEPENDS or PACKAGECONFIG? [build-deps] python-2.7.11: /usr/lib/python2.7/lib-dynload/_tkinter.so contained in package python-tkinter requires libtk8.6.so, but no providers found in RDEPENDS_python-tkinter? [file-rdeps] python3-3.5.1: python3-tkinter rdepends on tcl-lib, but it isn't a build dependency, missing tcl in DEPENDS or PACKAGECONFIG? [build-deps] python3-3.5.1: /usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-arm-linux-gnueabi.so contained in package python3-tkinter requires libtk8.6.so, but no providers found in RDEPENDS_python3-tkinter? [file-rdeps] (From OE-Core rev: 8cc5e36cd7978186d5ea1fe8af2f2bd6b3df8885) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2016-03-25 10:29:14 +00:00
bitbake	bitbake: bitbake: xmlrpc: set single use mode differently	2016-03-24 12:31:50 +00:00
documentation	sdk-manual: Added note for running remote apps with SSH port forw enabled.	2016-03-23 21:56:10 +00:00
meta	python(3): Disable tkinter	2016-03-25 10:29:14 +00:00
meta-poky	local.conf.sample: Disable prelink by default	2016-03-13 22:09:05 +00:00
meta-selftest	selftest/signing.py: RPM_GPG_PASSPHRASE_FILE -> RPM_GPG_PASSPHRASE	2016-03-25 10:29:14 +00:00
meta-skeleton	linux-yocto-custom: fix typo in Upstream-Status tag	2015-10-19 17:57:58 +01: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: Update SRCREV for genericx86* for 4.4	2016-03-07 00:11:40 +00:00
scripts	oe-publish-sdk: fix remote publishing	2016-03-25 10:29:14 +00:00
.gitignore	gitignore: fix overzealous exclusion	2015-11-16 11:39:38 +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: drop mention of binary-only drivers	2015-08-25 10:47:19 +01: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.