暫無描述

Michael Wood 310a9e5d35 bitbake: toaster: runbuilds Write the pidfile in python rather than shell script 8 年之前
bitbake 310a9e5d35 bitbake: toaster: runbuilds Write the pidfile in python rather than shell script 8 年之前
documentation 12a0ee049e dev-manual: Added note about RPM not dealing with post-install 8 年之前
meta 1d0c124cdf ruby: upgrade to 2.3.1 8 年之前
meta-poky d351c87452 maintainers: Change maintainers for python(3) modules 8 年之前
meta-selftest 39fba4d70f oe-selftest: devtool: test that updating a file with subdir= works 8 年之前
meta-skeleton 7e5b59d7af Remove $COREBASE/LICENSE from LIC_FILES_CHKSUM 8 年之前
meta-yocto 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 年之前
meta-yocto-bsp 0cdbd2ad94 conf: Remove legacy X input drivers 8 年之前
scripts 70f99b427b bb-perf: plot histograms base on buildstats data 8 年之前
.gitignore 5005cab723 add !meta-poky to .gitignore file 9 年之前
.templateconf 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 年之前
LICENSE ef91193c51 Fix license notices for OE-Core 11 年之前
README 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 年之前
README.hardware 9ba7226744 README.hardware: minor update to edgerouter section 8 年之前
oe-init-build-env dd5f2f7275 oe-init-build-env*: Make them actually return failures 9 年之前
oe-init-build-env-memres dd5f2f7275 oe-init-build-env*: Make them actually return failures 9 年之前

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.