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
12,210 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
Dexuan Cui fc1859ea66 recpies: add Upstream-Status for multiple recipes' patches 
tcf-agent: update its patch's Upstream-Status
screen: update its patch's Upstream-Status
which (GPLv2): update its patch's Upstream-Status
gnome-vfs: update its patch's Upstream-Status
libart-lgpl: update its patch's Upstream-Status
librsvg: update its patch's Upstream-Status
fontconfig: update its patch's Upstream-Status
freetype: update its patch's Upstream-Status
libxsettings-client: update its patch's Upstream-Status
libxcb: update its patch's Upstream-Status
libx11: update its patch's Upstream-Status
 - remove 2 unused xim.patch.
libx11-trim: update its patch's Upstream-Status
libxcalibrate: update its patch's Upstream-Status
libxcomposite: update its patch's Upstream-Status
libxfont: update its patch's Upstream-Status
xtrans: update its patch's Upstream-Status
  - remove abstract_socket_fix.patch as it's not used at all for long.
calibrateproto: update its patch's Upstream-Status
latencytop: update its patch's Upstream-Status
powertop: update its patch's Upstream-Status
settings-daemon: update its patch's Upstream-Status
gnome-settings-daemon: update its patch's Upstream-Status
libxklavier: update its patch's Upstream-Status
liblbxutil: update its patch's Upstream-Status
oprofile: update its patch's Upstream-Status and remove an unused patch
  - delete xml_callgraph_details.patch as it's not used at all.

(From OE-Core rev: 94991fb73586887bfc740eacf190032dfb206a65)

Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
 		2011-05-13 10:28:59 +01:00
bitbake codeparser.py: Ignore incomplete cache files 2011-05-12 23:39:20 +01:00
documentation documentation: Removed hardcoded user name from publish option 2011-05-10 10:02:17 +01:00
meta recpies: add Upstream-Status for multiple recipes' patches 2011-05-13 10:28:59 +01:00
meta-demoapps recpies: add Upstream-Status for multiple recipes' patches 2011-05-13 10:28:59 +01:00
meta-rt Rename poky-image-* -> core-image-* and task-poky-* -> task-core-* 2011-04-21 00:29:30 +01:00
meta-yocto conf/distro/include/default-distrovars.inc: Create set of default 'distro' variable values 2011-05-11 15:26:32 +01:00
scripts scripts/oe-setup-builddir: fix typo 2011-05-10 09:56:20 +01:00
.gitignore Rename the remaining poky-* scripts to oe-* or runqemu-* 2011-04-21 00:29:31 +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 Rename poky-image-* -> core-image-* and task-poky-* -> task-core-* 2011-04-21 00:29:30 +01:00
oe-init-build-env Further cleanup of various poky references 2011-04-21 12:56:16 +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/