OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Harald Welte fa0881442f make bitbake git fetcher use https:// instead of git:// protocol by default 7 months ago
bitbake make bitbake git fetcher use https:// instead of git:// protocol by default 7 months ago
documentation poky.ent: Updated the release date to July 2018. 4 years ago
meta build-appliance-image: Update to pyro head revision 4 years ago
meta-poky poky: Update version to 2.3.4 4 years ago
meta-selftest wic-image-minimal: stop using core-image-minimal 5 years ago
meta-skeleton useradd-example: exclude from world 6 years ago
meta-yocto/conf meta-yocto: Rename to meta-poky to better match its purpose 7 years ago
meta-yocto-bsp linux-yocto/4.1: generix86* bsp fix perf issue with gcc >=7 5 years ago
scripts scripts/test-dependencies.sh: remove 4 years ago
.gitignore add !meta-poky to .gitignore file 6 years ago
.templateconf meta-yocto: Rename to meta-poky to better match its purpose 7 years ago
LICENSE Fix license notices for OE-Core 9 years ago
README meta-yocto: Rename to meta-poky to better match its purpose 7 years ago
README.hardware README.hardware: update MPC8315E-RDB section 6 years ago
oe-init-build-env oe-init-build-env*: Make them actually return failures 6 years ago
oe-init-build-env-memres oe-init-build-env*: Make them actually return failures 6 years ago

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-poky, 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.