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 f04fb8806c scripts/create-pull-request: fix git request-pull syntax * at least with git 2.6.3 I see git request-pull failing when there is only :{BRANCH} as ending commit * $ git request-pull origin/dizzy git://git.openembedded.org/openembedded-core-contrib jansa/dizzy-backports:jansa/dizzy-backports The following changes since commit 7bb182bdd130266100fc541fd09b82d09c51cd80: build-appliance-image: Update to dizzy head revision (2015-09-29 14:56:04 +0100) ... And finds correct 7 changes there * $ git request-pull origin/dizzy git://git.openembedded.org/openembedded-core-contrib :jansa/dizzy-backports warn: No match for commit 6068d1c90336ddc1fb32856efd1d9ccf07733896 found at git://git.openembedded.org/openembedded-core-contrib warn: Are you sure you pushed 'jansa/dizzy-backports' there? The following changes since commit 97756472d3a69eaca95d105494ffea78c6b077e0: build-appliance-image: Update to dizzy head revision (2014-10-18 16:16:27 +0200) ... and lists all commits in _current_ branch since origin/dizzy, then it refuses to continue, because there are too many changes. * 6068d1c90336ddc1fb32856efd1d9ccf07733896 is this commit in jansa/master-submitted branch so it really shouldn't be included in pull request from jansa/dizzy branch. * git help says: <end> Commit to end at (defaults to HEAD). This names the commit at the tip of the history you are asking to be pulled. When the repository named by <url> has the commit at a tip of a ref that is different from the ref you have locally, you can use the <local>:<remote> syntax, to have its local name, a colon :, and its remote name. * maybe the syntax got changes since git 2.1.0 when Saul added :${BRANCH} * I haven't found how to respect ${COMMIT_ID in the new syntax (From OE-Core rev: 2336d1e5de671f538f0cd493b75d29e1dfdb0caf) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2016-01-11 23:26:32 +00:00
bitbake	bitbake: fetch/git: Change to use clearer ssh url syntax for broken servers	2016-01-08 13:58:08 +00:00
documentation	toaster-manual: Updates to toaster use chapter.	2016-01-07 12:13:46 +00:00
meta	qt4: fix-for-mips-n32.patch: remove it	2016-01-11 23:26:32 +00:00
meta-selftest	oeqa/selftest/signing: New test for Signing packages in the package feeds.	2015-11-24 15:55:41 +00:00
meta-skeleton	linux-yocto-custom: fix typo in Upstream-Status tag	2015-10-19 17:57:58 +01:00
meta-yocto	maintainers.inc: remove x11vnc	2016-01-08 13:57:32 +00:00
meta-yocto-bsp	meta-yocto-bsp: remove 3.14 and 3.19 bbappends	2015-12-28 09:25:30 +00:00
scripts	scripts/create-pull-request: fix git request-pull syntax	2016-01-11 23:26:32 +00:00
.gitignore	gitignore: fix overzealous exclusion	2015-11-16 11:39:38 +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: drop mention of binary-only drivers	2015-08-25 10:47:19 +01:00
oe-init-build-env	scripts: hand the TEMPLATECONF local over to setup-builddir	2015-12-28 09:25:19 +00: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.