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
Scott Rifenbark 684c35b7aa documentation: Changed all manual links to point to "latest"
There are many references to YP documentation throughout the
YP manual set.  They used to have hard-coded links to the
current release (e.g. yoctoproject.org/docs/1.1 for Edison).
This created a situation where if you went to a document on
the website and clicked on a external reference to another
manual, you would redirect to the current manual on the website.
Really, you would want to go to the latest manual, which is
one that is under development.  Changing the links to
"yoctoproject.org/docs/latest" makes the tip of master, which
is used for devloping the next release, always have references
to the manuals being developed and not back to the stable
released set of manuals.

This "latest" and "current" scheme for the links is not perfect.
What has to happen when the latest set of the manuals freezes
and becomes the next stable release, all the links in the docs
will need to be changed from "latest" in the URL to the new
release number.  So for example, all the "latest" occurences
would need to be changed to "1.2".  Then for the next cycle
as development begins again, the links need to be infused with
"latest" again.

(From yocto-docs rev: a234aef34303b07671da956de0e94b352797143e)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-25 15:24:17 +00:00
bitbake bitbake/siggen.py: Don't backtrace if the taskhash data isn't present 2011-11-25 11:25:59 +00:00
documentation documentation: Changed all manual links to point to "latest" 2011-11-25 15:24:17 +00:00
meta ofono: Fix missing python dependency and package tests separately 2011-11-25 11:40:00 +00:00
meta-demoapps Convert to use direct access to the data store (instead of bb.data.*Var*()) 2011-11-10 11:51:19 +00:00
meta-skeleton useradd-example.bb: update example documentation comments 2011-11-10 11:37:12 +00:00
meta-yocto netbase: update 4.46 -> 4.47 2011-11-21 18:49:40 +00:00
scripts sanitytest: use different option for command ps from busybox and procps 2011-11-18 10:47:15 +00:00
.gitignore Update gitignore to ignore all meta-* directories 2011-10-04 13:46:24 +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 README.hardware: declare support for BeagleBoard xM rev B 2011-11-10 18:07:52 +00:00
oe-init-build-env oe-init-build-env, scripts/oe-buildenv-internal: add error detecting for $BDIR 2011-08-02 14:32:10 +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/