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
Nitin A Kamble 771d890d08 eglibc: rebase a nativesdk patch to the newer code
After the eglibc svn commit bumping, this nativesdk recipe's patch is
failing. This commit rebases it to the newer code.

and bump PR.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2010-11-18 10:38:35 -08:00
bitbake siggen.py: fix comparison around runtaskdeps 2010-11-15 23:04:06 +00:00
documentation Poky Reference Manual: General edits up to the "Debugging with GDB Remotely" section. 2010-11-15 22:25:26 +00:00
meta eglibc: rebase a nativesdk patch to the newer code 2010-11-18 10:38:35 -08:00
meta-emenlow meta-emenlow: Rename packages to recipes in line with main repository 2010-11-02 10:08:00 +00:00
scripts poky-qemu: Fix issues when running Yocto 0.9 release images 2010-11-14 21:08:28 -08:00
.gitignore gitignore: ignore the default downloads directory 2010-11-14 21:08:27 -08:00
LICENSE LICENSE: Clarify the license recipe source code is under 2010-06-10 10:13:18 +01:00
README README*: Update after addition of manual 2008-02-26 11:40:57 +00:00
README.hardware Fix broken string with weird characters. 2008-02-29 13:29:19 +00:00
poky-init-build-env poky-init-build-env: Fix to show the error message with simple sh based shells 2010-11-13 22:26:46 +08:00

README

Poky
====

Poky platform builder is a combined cross build system and development 
environment. It features support for building X11/Matchbox/GTK based 
filesystem images for various embedded devices and boards. It also 
supports cross-architecture application development using QEMU emulation
and a standalone toolchain and SDK with IDE integration.

Poky has an extensive handbook, the source of which is contained in
the handbook directory. For compiled HTML or pdf versions of this, 
see the Poky website http://pokylinux.org.

Additional information on the specifics of hardware that Poky supports
is available in README.hardware.