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,411 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
Darren Hart 3a454781df u-boot: rename u-boot_git.bb to u-boot_${PV}.bb 
In order to facilitate reuse of the oe-core u-boot recipe, there needs to be
some assurance that the oe-core version won't change without a clear indicator
to people extending it.

By renaming the recipe to include its version string instead of "git", BSP
layers can extend a specific base version of u-boot, ie.
u-boot_2011.03.bbappend. When 2011.06 becomes available, we can create that file
without instantly breaking all the BSPs depending on oe-core version of the
recipe.

As a matter of policy I would recommend we not carry more than 2 versioned
u-boot recipess at any given time. This will provide BSP layers time to migrate
to the newer version, without cluttering oe-core with numerous stale versions of
u-boot. We may decide later to resurrect u-boot_git.bb as an AUTOREV recipe to
faciliate upstream development on u-boot in the oe environment.

(From OE-Core rev: f788d4b503ecc6600612746c4936dfb9393e237c)

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Cc: Jason Kridner <jkridner@beagleboard.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
 		2011-05-27 16:38:53 +01:00
bitbake cooker.py: Don't show spurious warnings for collections of .bbappend files 2011-05-25 23:47:22 +01:00
documentation documentation/yocto-project-qs/yocto-project-qs.xml: fixed build env script 2011-05-23 15:53:29 +01:00
meta u-boot: rename u-boot_git.bb to u-boot_${PV}.bb 2011-05-27 16:38:53 +01:00
meta-demoapps recipes: Add Upstream-Status to multiple recipes 2011-05-13 10:29:01 +01:00
meta-rt Rename poky-image-* -> core-image-* and task-poky-* -> task-core-* 2011-04-21 00:29:30 +01:00
meta-skeleton Add a skeleton for init scripts 2011-05-18 14:32:45 +01:00
meta-yocto IMAGE_ROOTFS_SIZE: Cleanup machine conf files 2011-05-25 14:07:37 -07:00
scripts create-pull-request: generalize the repository URL parsing 2011-05-25 15:50:54 +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 README.hardware: update installation instructions for beagleboard 2011-05-25 16:21:51 -07: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/