sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity
OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705
27,328 Commits 8 Branches 0 Tags 142 MiB
Python 37.9%
BitBake 15.7%
C 15.5%
PHP 10%
Shell 7.2%
Other 13.4%
Go to file
Richard Purdie a4457cf939 bitbake: siggen: When printing signatures recursively, limit the output 
Currently the code prints all differences. If the task dependencies have changed hash,
we recurse into those and print those differences as well. This leads to a lot
of output. The reality is if the parents changed signature, we might as well just
say that and recurse with no other output since we're much more interested in how
the parents changed in nearly all cases. The changes in the parent are probably
the same ones we'd have printed at each level anyway.

By doing this we focus the output more carefully on the thing the user wants/needs
to see.

(Bitbake rev: 7a17fd6e51a76d3582c357b79f5ef86e1969650c)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
 		2013-12-20 12:26:05 +00:00
bitbake bitbake: siggen: When printing signatures recursively, limit the output 2013-12-20 12:26:05 +00:00
documentation ref-manual: Fixed the reference to the script for icecc class. 2013-12-13 16:30:02 +00:00
meta security_flags: more relocation issues 2013-12-18 17:24:07 +00:00
meta-hob meta-*/conf/layer.conf: tweak BBFILES comment 2013-04-10 09:23:17 +01:00
meta-selftest meta-selftest: create a new test layer to be used by oe-selftest script 2013-12-03 17:45:50 +00:00
meta-skeleton useradd-example: add example for setting clear text password 2013-12-14 09:16:38 +00:00
meta-yocto meta-toolchain-sdk: Remove references from meta-yocto 2013-12-19 09:45:21 +00:00
meta-yocto-bsp meta-yocto-bsp: Drop gmae bbappends to match OE-Core 2013-12-05 14:25:31 +00:00
scripts scripts/contrib: Add graph-tool 2013-12-18 11:21:27 +00:00
.gitignore .gitignore: Add meta-yocto-imported 2013-12-09 15:57:27 +00:00
LICENSE LICENSE: Clarify the license recipe source code is under 2010-06-10 10:13:18 +01:00
README README: Clarify where to send patches 2012-08-22 14:05:00 +01:00
README.hardware README.hardware: update genericx86 hardware support 2013-10-01 23:08:21 +01:00
oe-init-build-env oe-init-build-env: Allow startup with and without memres 2013-12-02 11:28:27 +00:00
oe-init-build-env-memres oe-init-build-env-memres: Add auto port functionality 2013-12-02 11:28:27 +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 = "") 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.