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
Roxana Ciobanu 6a77a1dd22 scripts/send-error-report: fetch /Errors/ instead of /.
If HTTP_PROXY or http_proxy is set when the send-error-report script
is run, it will check to see if fetching / on the specified server
returns 200 without the proxy set. If it does it will assume that the
proxy is not needed. However this check can never work because
fetching / always redirects to /Errors/ in the current code and
thus returns code 301. This is fixed by fetching /Errors/ instead of /.

[YOCTO #YB6576]

(From OE-Core rev: af93c89febcd186d7e31f1d15affc15f38e3379d)

Signed-off-by: Roxana Ciobanu <roxana.ciobanu@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-08-06 10:23:39 +01:00
bitbake bitbake: runqueue: Add sceneQueueComplete event 2014-08-03 12:40:41 +01:00
documentation dev-manual: Updates for checksums and wic 2014-08-02 10:00:26 +01:00
meta gstreamer1.0-omx: Remove unnecessary dependency on plugins-bad. 2014-08-06 10:23:39 +01:00
meta-selftest Basic recipe formatting fixes 2014-01-02 12:50:21 +00:00
meta-skeleton linux-yocto-custom: provide defconfig guidance 2014-05-06 17:59:17 +01:00
meta-yocto local.conf.sample.extended: fix example for EXTRA_USERS_PARAMS 2014-08-04 17:38:24 +01:00
meta-yocto-bsp oeqa/controllers/beaglebonetarget.py: fix deploy when kernel file is a broken link 2014-07-17 14:56:49 +01:00
scripts scripts/send-error-report: fetch /Errors/ instead of /. 2014-08-06 10:23:39 +01:00
.gitignore bitbake: gitignore: Update for recent docs changes 2014-01-27 21:03:13 +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: fix DISTRO = "" reference 2014-01-02 12:58:54 +00:00
README.hardware mpc8315e-rdb: add the example about booting from jffs2 root 2014-06-17 17:56:22 +01:00
oe-init-build-env oe-init-build-env: Improve script sourcing detection. 2014-03-11 08:11:41 -07: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 = "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, 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.