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
Bruce Ashfield 408fd37529 fetch2/git: create bareclone option
For similar reasons as the nocheckout option, packages that need
enhanced control over the checkout and branch creation on a repository
may want a complete mirror/bareclone created of the repository when
performing the unpack.

This is useful/required when a local respository is being used, but
local tracking branches have not been created for all branches that
a given recipe needs to manipulate. The standard git clone operations
will create remote branches for the branches that are local to the
source repository, but branches that are remote do not translate to
the destination repository. Doing a mirror/bare clone of the source,
makes all branches available to the repository.

This is a particular use case, but the ability to do a bare clone
creates great flexibility in recipe space, with no impact to recipes
that don't need this functionality.

To implement this, a new option 'bareclone' is craeted which creates
a mirror copy of the repository and leaves it bare in the unpacking
phase. A recipe that uses this option must both checkout and debare
the repository itself.

(Bitbake rev: 82482aae6f311c994275fb0b6b32d954bbfc78c3)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-02-24 16:40:08 +00:00
bitbake fetch2/git: create bareclone option 2012-02-24 16:40:08 +00:00
documentation documentation/yocto-project-qs/yocto-project-qs.xml: removed disable dash text 2012-01-06 12:13:13 +00:00
meta conf/bitbake.conf: add DISTRO_FEATURES_BACKFILL 2012-02-24 16:37:07 +00:00
meta-demoapps Add Upstream-Status to patches 2012-01-03 12:14:31 +00:00
meta-hob meta-hob: Add a new meta-hob layer 2012-02-24 00:39:10 +00:00
meta-skeleton useradd-example.bb: update example documentation comments 2011-11-10 11:37:12 +00:00
meta-yocto meta-yocto: Add abi_version setting version 8, to match the OEBasicHash change and trigger warnings for existing build directories 2012-02-22 22:06:11 +00:00
scripts A script to clean obsolete sstate cache files 2012-02-23 23:59:40 +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: add short description of OE-Core 2012-01-05 11:24:01 +00: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

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/