sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity
OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705
21,126 Commits 8 Branches 0 Tags 142 MiB
Python 37.9%
BitBake 15.7%
C 15.5%
PHP 10%
Shell 7.2%
Other 13.4%
Go to file
Constantin Musca a0a265e352 poky-tiny.conf: blacklist inappropriate image options 
Blacklist all images that fail when using poky-tiny

poky-tiny image tests:
1. build-appliance-image
    * ERROR: Nothing RPROVIDES libx11-dev
2. core-image-minimal-*
    * ok
3. core-image-base
    * libcap fails at do_compile
4. core-image-basic
    * libcap fails at do_compile
5. core-image-clutter
    * ERROR: Nothing PROVIDES virtual/libx11
6. core-image-gtk-directfb
    * ERROR: Nothing RPROVIDES libxt
7. core-image-lsb, core-image-lsb-dev, core-image-lsb-sdk
    * ERROR: Nothing RPROVIDES libxt
8. core-image-rt
    * ERROR: Multiple .bb files are due to be built which each provide virtual/kernel
        (/home/dev/yocto/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
            /home/dev/yocto/poky/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb).
9. core-image-rt-sdk
    * ERROR: Nothing PROVIDES xext
10. core-image-sato, core-image-sato-dev, core-image-sato-sdk
    * ERROR: Nothing PROVIDES libxft
11. core-image-x11
    * ERROR: Nothing PROVIDES virtual/libx11
12. q4te-demo-image
    * libcap fails at do_compile

[YOCTO #2565]

(From meta-yocto rev: 6b6d84b6652f57ea8dd37e6921c280d30ef04b93)

Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
 		2012-12-13 16:54:35 +00:00
bitbake bitbake: BBhandler/data: Fix __inherit_cache duplication 2012-12-11 15:59:42 +00:00
documentation Documentation: poky-ref-manual - Updates to WORKDIR structure 2012-12-11 16:17:57 +00:00
meta chrpath: normalize the paths 2012-12-13 16:54:31 +00:00
meta-hob hob-toolchain: Update for removal of dummy classes 2012-12-11 12:39:07 +00:00
meta-skeleton linux-yocto-custom: Clarify defconfig usage 2012-10-03 10:03:08 +01:00
meta-yocto poky-tiny.conf: blacklist inappropriate image options 2012-12-13 16:54:35 +00:00
meta-yocto-bsp mesa: remove atom-pc specific overrides 2012-12-06 13:51:38 +00:00
scripts yocto-kernel: add support for PRs of the form rN to pr_inc() 2012-12-13 16:54:35 +00:00
.gitignore gitignore: Fix for poky repository 2012-10-11 13:52:14 +01:00
LICENSE LICENSE: Clarify the license recipe source code is under 2010-06-10 10:13:18 +01:00
README README: Clarify where to send patches 2012-08-22 14:05:00 +01:00
README.hardware README.hardware: extend USB-ZIP instructions 2012-04-01 12:52:03 +01:00
oe-init-build-env Various typoes fixed, all comments or output strings. 2012-03-26 12:13:05 +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/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/

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.