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

Paul Eggleton 7d5c9860de bitbake: tinfoil: rewrite as a wrapper around the UI Rewrite tinfoil as a wrapper around the UI, instead of the earlier approach of starting up just enough of cooker to do what we want. This has several advantages: * It now works when bitbake is memory-resident instead of failing with "ERROR: Only one copy of bitbake should be run against a build directory". * We can now connect an actual UI, thus you get things like the recipe parsing / cache loading progress bar and parse error handling for free * We can now handle events generated by the server if we wish to do so * We can potentially extend this to do more stuff, e.g. actually running build operations - this needs to be made more practical before we can use it though (since you effectively have to become the UI yourself for this at the moment.) The downside is that tinfoil no longer has direct access to cooker, the global datastore, or the cache. To mitigate this I have extended data_smart to provide remote access capability for the datastore, and created "fake" cooker and cooker.recipecache / cooker.collection adapter objects in order to avoid breaking too many tinfoil-using scripts that might be out there (we've never officially documented tinfoil or BitBake's internal code, but we can still make accommodations where practical). I've at least gone far enough to support all of the utilities that use tinfoil in OE-Core with some changes, but I know there are scripts such as Chris Larson's "bb" out there that do make other calls into BitBake code that I'm not currently providing access to through the adapters. Part of the fix for [YOCTO #5470]. (Bitbake rev: 3bbf8d611c859f74d563778115677a04f5c4ab43) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2016-12-14 12:25:07 +00:00
bitbake	bitbake: tinfoil: rewrite as a wrapper around the UI	2016-12-14 12:25:07 +00:00
documentation	sdk-manual: Added note about nullpointer error for launch eclipse	2016-12-08 16:36:40 +00:00
meta	libpcap: Disable exposed bits of WinPCAP remote capture support	2016-12-13 22:55:22 +00:00
meta-poky	libc-package.bbclass: split binary localedata even more if asked to	2016-12-08 10:35:08 +00:00
meta-selftest	recipetool: selftest: Add test for recipetool plugin loading	2016-12-13 22:55:20 +00:00
meta-skeleton	Remove $COREBASE/LICENSE from LIC_FILES_CHKSUM	2016-10-28 16:15:18 +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	edgerouter.conf: enable generation of wic.bmap	2016-12-14 09:29:11 +00:00
scripts	oe-buildenv-internal: show usage output	2016-12-13 22:55:21 +00: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: minor update to edgerouter section	2016-10-28 16:32:31 +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.