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
Richard Purdie c8928e93dd bitbake/cooker/codeparser: Ensure the code parser cache is saved for each parsing process
Before this change, the codeparser cache was only being saved for the main
server process. This is suboptimal as it leaves code being re-evaluated at
task execution time and increases parse time.

We use the multiprocess Finalize() functionality to ensure each process
saves out its cache. We need to update the cache save function to be multiprocess
friendly with locking.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-05 15:52:53 +01:00
bitbake bitbake/cooker/codeparser: Ensure the code parser cache is saved for each parsing process 2011-05-05 15:52:53 +01:00
documentation Rename poky-image.bbclass to core-image.bbclass 2011-04-21 13:08:47 +01:00
meta boot-directdisk: fix bzImage source location 2011-05-05 12:26:48 +01:00
meta-demoapps Remove distro-specific metadata for distros not in oe-core 2011-05-05 12:26:30 +01:00
meta-rt Rename poky-image-* -> core-image-* and task-poky-* -> task-core-* 2011-04-21 00:29:30 +01:00
meta-yocto meta-yocto: add pieces removed from oe-core for beagleboard & atom-pc 2011-05-05 12:25:59 +01:00
scripts qemuimagetest: Add executable permission to test scripts for toolchain 2011-05-04 08:57:28 +01:00
.gitignore Rename the remaining poky-* scripts to oe-* or runqemu-* 2011-04-21 00:29:31 +01:00
LICENSE LICENSE: Clarify the license recipe source code is under 2010-06-10 10:13:18 +01:00
README README: Update to reflect what Poky is today 2011-04-21 13:03:52 +01:00
README.hardware Rename poky-image-* -> core-image-* and task-poky-* -> task-core-* 2011-04-21 00:29:30 +01:00
oe-init-build-env Further cleanup of various poky references 2011-04-21 12:56:16 +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/community/documentation

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