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
34,017 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
Patrick Ohly dcb8f89723 combo-layer: improve merge commit handling 
When the head of a branch is a merge commit, combo-layer did not
record that commit as last_revision because it only considers applied
patches, and the merge commit never gets applied.

This causes problems when the merge commit leads to multiple patches
and the commit id that gets recorded only reaches some of these
patches. The next run then will try to re-apply the other patches.

This special case is now detected and dealt with by bumping
last_revision to the branch commit. The behavior where the head is a
normal commit is intentionally not changed, because some users might
prefer the traditional behavior.

(From OE-Core rev: 701bcd52c208f22a9a6c48a11a35bcf1c4e413df)

Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
 		2015-05-09 22:26:45 +01:00
bitbake bitbake: prserv: serv.py: remove unused and duplicate imports 2015-05-08 17:46:36 +01:00
documentation dev-manual: Updates to add Luna support for Eclipse 2015-05-03 11:49:35 +01:00
meta weston-init: support system's configuration file 2015-05-09 22:26:45 +01:00
meta-selftest oe-selftest: add a test for devtool deploy-target 2015-03-20 11:27:48 +00:00
meta-skeleton skeleton: clarify linux-yocto-custom workflow 2015-03-25 12:39:48 +00:00
meta-yocto poky.conf: remove SVK mirror 2015-05-05 22:18:23 +01:00
meta-yocto-bsp meta-yocto-bsps: remove 3.10 bbappend 2015-02-21 22:05:37 +00:00
scripts combo-layer: improve merge commit handling 2015-05-09 22:26:45 +01:00
.gitignore gitignore: exclude meta-selftest, drop meta-hob 2015-03-20 11:27:47 +00:00
.templateconf .templateconf: New file for customized template defaults 2014-03-11 08:14:27 -07:00
LICENSE Fix license notices for OE-Core 2014-01-02 12:58:54 +00:00
README README: expand the Where To Send Patches section 2015-03-04 17:07:37 +00:00
README.hardware README.hardware: clarify NFS requirements for edgerouter 2015-03-31 22:23:20 +01:00
oe-init-build-env oe-init-build-env: fix for build dirs that have spaces in their path 2015-04-13 22:33:24 +01:00
oe-init-build-env-memres oe-init-build-env-memres: Fix source check 2015-03-20 10:56:03 +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-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.